1. Lawrence Micheal
  2. PowerBuilder
  3. Tuesday, 31 October 2023 01:00 AM UTC

Team,

We have an application called Occusource which is getting XML feed from other system and verifying in Occusouce by using XMLParseString function. We are facing issue like if there is any special character on the XML then it is returning -1 and throwing invalid XML error as per our code. Here I have 2 questions.

1. Do we have any functions filter special characters/non-ascii characters? Since we dont what special characters came in that XML, we cannot go with REPLACE function until we know the special character to be removed.

2. I am noticing this XMLParseString is not working as expected, we have an XML string which is having non-ascii special character in it, if I validate that XML in XML validator websites it say XML is valid, but PB built in function XMLParseString is throwing error. So we are confused with this result, can you please confirm why the difference? How online XML validator is passing this XML with non-ascii and why our PB function is failing?

Attaching the XML and screen print from online XML validator.


20004048
136741150
Special
¹Characters
01/01/1991
M
10/30/2023
2 drug screens 1
3
94.70
10/30/2023
CCSUser
10/30/2023
CMC - DFW Las Colinas
32

 

 

 

 

 



There are no replies made for this question yet.
However, you are not allowed to reply to this question.
We use cookies which are necessary for the proper functioning of our websites. We also use cookies to analyze our traffic, improve your experience and provide social media features. If you continue to use this site, you consent to our use of cookies.