KB-1851 Web APIs return special characters as question marks

Jordan Horwat — Thu, 24 Jan 2019 21:31:17 GMT

Current Revision posted to Appian Knowledge Base by Jordan Horwat on 1/24/2019 9:31:17 PM

Symptoms

When querying a Web API, some special characters, such as the em dash (–), are incorrectly interpreted by clients such as SoapUI and Postman. The client displays these characters as question marks or other symbols of incompatibility, while Appian displays them as expected.

Result in Appian

Result in Client

Cause

This occurs when the Web API does not send an appropriate Content-Type header with a character set included, which the client system relies on to interpret the content sent by the Web API.

Action

Explicitly specify the Content-Type header with the relevant character set in the SAIL code for the Web API using a!httpHeader in the headers parameter of the a!httpResponse. For example, to correctly send JSON with the UTF-8 character set (which supports the em dash character), include the following:

headers: {
  a!httpHeader(
    name: "Content-Type",
    value: "application/json; charset=utf-8"
  )
}

Note: If the source data itself does not support these special characters, for example due to querying a database with a restrictive character set and collation, including the header will have no effect. If this is the case, Appian will also fail to render the characters as expected.

Affected Versions

This article applies to Appian 7.9 and later.

Last Reviewed: January 2019

Tags: SAIL, integration, web services, application design, web api

KB-1851 Web APIs return special characters as question marks

Jordan Horwat — Thu, 24 Jan 2019 16:31:17 GMT

Revision 7 posted to Appian Knowledge Base by Jordan Horwat on 1/24/2019 4:31:17 PM

Symptoms

Result in Appian

Result in Client

Cause

This occurs when the Web API does not send an appropriate Content-Type header with a character set included, which the client system relies on to interpret the content sent by the Web API.

Action

headers: {
  a!httpHeader(
    name: "Content-Type",
    value: "application/json; charset=utf-8"
  )
}

Affected Versions

This article applies to Appian 7.9 and later.

Last Reviewed: January 2019

Tags: SAIL, integration, web services, application design, web api

KB-XXXX Web APIs return special characters as question marks

Jordan Horwat — Thu, 24 Jan 2019 11:38:41 GMT

Revision 6 posted to Appian Knowledge Base by Jordan Horwat on 1/24/2019 11:38:41 AM

Symptoms

Result in Appian

Result in Client

Cause

This occurs when the Web API does not send an appropriate Content-Type header with a character set included, which the client system relies on to interpret the content sent by the Web API.

Action

headers: {
  a!httpHeader(
    name: "Content-Type",
    value: "application/json; charset=utf-8"
  )
}

Affected Versions

This article applies to Appian 7.9 and later.

Last Reviewed: January 2019

Tags: SAIL, integration, web services, application design, web api

KB-XXXX Web APIs return special characters as question marks

Jussi Lundstedt — Thu, 24 Jan 2019 11:19:59 GMT

Revision 5 posted to Appian Knowledge Base by Jussi Lundstedt on 1/24/2019 11:19:59 AM

Symptoms

When querying a Web API, some special characters, such as the em dash (–), are incorrectly interpreted by clients such as SoapUI and Postman as question marks or other symbols of incompatibility, while Appian displays them as expected.

Result in Appian

Result in Client

Cause

This issue is caused by the Web API not sending an appropriate Content-Type header with a character set included, which the client system relies on to interpret the content sent by the Web API.

Action

headers: {
  a!httpHeader(
    name: "Content-Type",
    value: "application/json; charset=utf-8"
  )
}

Note that if the source data itself does not support these special characters, for example due to querying a database with a restrictive character set and collation, including the header will have no effect. If this is the case, Appian will also fail to render the characters as expected.

Affected Versions

This article applies to Appian 7.9 and later.

Last Reviewed: January 2019

Tags: SAIL, integration, web services, application design, web api

KB-XXXX Web APIs return special characters as question marks

Jussi Lundstedt — Thu, 24 Jan 2019 11:19:28 GMT

Revision 4 posted to Appian Knowledge Base by Jussi Lundstedt on 1/24/2019 11:19:28 AM

Symptoms

Result in Appian

Result in Client

Cause

This issue is caused by the Web API not sending an appropriate Content-Type header with a character set included, which the client system relies on to interpret the content sent by the Web API.

Action

headers: {
  a!httpHeader(
    name: "Content-Type",
    value: "application/json; charset=utf-8"
  )
}

Note that if the source data itself does not support these special characters, for example due to querying a database with a restrictive character set and collation, including the header will not resolve this. If this is the case, Appian will also fail to render the characters as expected.

Affected Versions

This article applies to Appian 7.9 and later.

Last Reviewed: January 2019

Tags: SAIL, integration, web services, application design, web api

KB-XXXX Web APIs return special characters as question marks

Jussi Lundstedt — Thu, 24 Jan 2019 11:14:37 GMT

Revision 3 posted to Appian Knowledge Base by Jussi Lundstedt on 1/24/2019 11:14:37 AM

Symptoms

Result in Appian

Result in Client

Cause

This issue is caused by the Web API not sending an appropriate Content-Type header with a character set included, which the client system relies on to interpret the content sent by the Web API.

Action

headers: {
  a!httpHeader(
    name: "Content-Type",
    value: "application/json; charset=utf-8"
  )
}

Affected Versions

This article applies to Appian 7.9 and later.

Last Reviewed: January 2019

Tags: SAIL, integration, web services, application design, web api

KB-XXXX Web APIs return special characters as question marks

Jussi Lundstedt — Thu, 24 Jan 2019 11:13:08 GMT

Revision 2 posted to Appian Knowledge Base by Jussi Lundstedt on 1/24/2019 11:13:08 AM

Symptoms

Result in Appian

Result in Client

Cause

This issue is caused by the Web API not sending an appropriate Content-Type header with a character set included, which the client system relies on to interpret the content sent by the Web API.

Action

headers: {
  a!httpHeader(
    name: "Content-Type",
    value: "application/json; charset=utf-8"
  )
}

Affected Versions

This article applies to Appian 7.9 and later.

Last Reviewed: January 2019

Tags: SAIL, integration, web services, application design, web api

KB-XXXX Web APIs return special characters as question marks

Jussi Lundstedt — Tue, 22 Jan 2019 21:28:25 GMT

Revision 1 posted to Appian Knowledge Base by Jussi Lundstedt on 1/22/2019 9:28:25 PM

Symptoms

Cause

Action

Affected Versions

This article applies to Appian 7.9 and later.

Last Reviewed: January 2019

Tags: SAIL, integration, web services, application design, web api