I had a similar issue recently with Danish characters in an R/R pair. We tried using CP1252 as an encoding during recording, but that failed as well.
The issue was that SoapUI (which was the client) did not have its encoding set to UTF-8. When the request was sent to the service, SoapUI replaced the characters with special characters similar to your earlier screenshot. The result was that the request never matched in the VSI because the incoming request did not contain actual Danish characters.
The service worked correctly on my US-based machine from both SoapUI and Postman, but not on the customer's machine.
When the customer changed the SoapUI encoding to UTF-8, the issue went away.
Original Message:
Sent: 07-23-2019 06:07 AM
From: Raghu Krishna
Subject: Special Characters not read in REST based JSON response in 10.4
I dont think this is the issue.
I have created virtual service using 10.2 version and it was reading the file. Whereas when I try to create using 10.4, it is not able to read.
I have attached R & R for reference, please help and try to replicate.
we have done the devtest upgrade recently to 10.4. Could this issue be related to the latest version?
Original Message:
Sent: 07-23-2019 02:46 AM
From: Vaibhav Jain
Subject: Special Characters not read in REST based JSON response in 10.4
Try using other encodings like windows-1250. It works for special chars.
Thanks.
Original Message:
Sent: 07-23-2019 01:00 AM
From: Raghu Krishna
Subject: Special Characters not read in REST based JSON response in 10.4
May I request you to explain in detail please? I have been creating virtual services with these kind of response and special characters and never faced such issue.
Original Message:
Sent: 07-23-2019 12:53 AM
From: Keith Jones
Subject: Special Characters not read in REST based JSON response in 10.4
To write scripts that administer Portal for ArcGIS, you need to choose a scripting language that allows you to construct URLs, make HTTP requests, and parse telldunkin