on 09-20-2013 7:21 AM
Hi Frnds,
The objective is to encode the characters outside the ASCII character set (Thai characters in this instance) inside the XML document that we exchange between X and CRM to perform searches, updates etc.. The XML documents in both directions (X->CRM and CRM->X) for the Thai market must contain this technique of encoding to enable non ASCII characters.
Characters are encoded as &#nnnn;
Where nnnn is the decimal numeric representation of the character. The ‘&#’ and ‘;’ are (ASCII) string constants.
Can any body suggest Soap adapter and RFC adapter can handle the above requirement.
Regards,
Narendra
Hi Narendra,
Have no fear, Unicode is the native format of PI. Simply make sure to set the encoding to ASCII on one side, and UTF-8 on the other, PI will take care of the conversion.
Regards,
Greg
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Narendra,
Check if this link is helpful
SAP Note 856597 - FAQ: XI 3.0 SOAP Adapter
Regards
Abhishek
Hi I have gone through the link which you have provided.document says we have to provide the url as below:
Url:
http://host:port/XISOAPAdapter/MessageServlet?channel=p:s:c&xmlen
c=iso-8859-1
Already we have developed 4 countries markets earlier for english,Now for the same scenario we need to configure to handle unicode data as discussed above.
Here my concerns:
1)if we maintain new url,will Existing functionality will effect?
2)with out affecting existing functionality how can i configure soap channel at sender side?
3)I have seen in some posts they have used below parameter for reciver channel,But my case is at sender. So will these parameters will work for sender soap channel?
Below is the example how we get the data TO CRM/FROM CRM
Html Unicode encoding:
English text: Nare
Unicoded text to/from CRM: Exit
Please suggest....
Regards,
Narendra
Hi Narendra,
Did you get solution to handle &#xnnn characters in XML?
I am getting the control characters in response of a synch soap call. I tried changing the encoding to iso-8859-1 but still the error is same.
Sender Soap Endpoint:
Please suggest!
Regards,
Indu Khurana.
User | Count |
---|---|
87 | |
10 | |
10 | |
10 | |
7 | |
6 | |
6 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.