I use Appian cloud and yesterday evenning, I upgraded to the 20.1 version.
Since this upgrade, I have encoding issues with my integrations results that I did not have before.
The results are in JSON format and every value that contains special characters are now not "correctly" displayed/returned : VÃ©hicule instead of Véhicule
When I do the same request with Postman or my web browers, I have the results well encoded (Véhicule).
Does someone have the same issue ?
Does someone have a solution about this ?
Hello Julien, I have exactly the same problem. Did you have any answer from the Appian support ?
If I understood well the support, with 20.1 version, they added the following behaviour to the integration components :
- if there is no charset defined in the Http Response, Appian set the encoding with the default value ISO_8859_1
- if the charset is defined, Appian uses the charset from the response
Actually, it seems that the only way is to configure your API to send the charset in the respons : Content-Type: application/json;charset=UTF-8
It worked for me.
Thank you for your response. If I understand correctly, this will work while defining a Web API component, where the header can be forced in the httpResponse function. But If I'm using an Integration component, is there a way to define the charset of the response ? I can define it as a request header, but I'm still having issues with the response.
I don't think there is a way (or I have not find it) to define the charset of the response in an integration component.
I am submitting a product enhancement request to add afield on the integration component configuration view that allows the user to set the default charset setting.
Discussion posts and replies are publicly visible
© 2020 Appian. All rights reserved.