|
Description |
|
|
On SQL Server DB, when testing the REST API to insert data in a double-byte characters set language, for example in Hebrew, it results in data saved on the DB as just a succession of question marks. Entering the same Hebrew string from the front end (for the same field) works just fine. *Steps to reproduce:* # have an environment set up for EAM v12.0 pointing to a SQL Server DB, open the swagger page # select the Operations > Call Center menu item # fill in eamhost and authorize the user # select the POST /contactrecords option, click on Try Out and populate tenant and organization # use the attached sample JSON data to run and insert a record on table R5CONTACTRECORDS, where CTR_DESC and CTR_FIRSTNAME are passed as Hebrew string *Expected result:* The result should show the Hebrew string for the updated fields, as well as the Hebrew string should be visible from the DB and from the record in EAM *Actual result:* The result from the swagger already shows question marks, which can also be seen from the DB and base EAM. |
|