I have & in one for the XML document data. When i am trying to read that document and doing operation & is breaking the system to read XML profile. How can I fix this issue?
can you show an example of the problem data and give more details on what you mean by "breaking the system"?
Bring in a DP and do a search and replace reserved symbols to actual. Then pass to build your XML. In your case Search for & and replace with &.
You may refer the link below for more
Inconsistently Translated XML Reserved Symbols
that article is a bit misleading. the only "controversial" character is the ">", for which escaping is optional in the xml spec. most xml parsers handle that just fine, but some poorly written parsers require it to be escaped.
Does this link open for you?
It says Unauthorized, Not sure on the maintenance activity.
Can you verify once and let us know Britto Parthalomew
Same here Srini
Since the content was misleading it might have been removed.
Yes, the article was pulled for an internal review.
Is that the only solution? XML can break with any special character right? Here is the example
<item> <ItemNo>0943</ItemNo> <ItemName>Hotel & Suites Arizona</ItemName> <CRMId>0016000000xtvdu</CRMId> <ItemType>Hotel</ItemType> <UpdateStatus>X</UpdateStatus></Item>
I could not able to read this profile when I am sending this to XML Profile. Other than search & Replace is there any other settings that we can change and make it work?
That xml is perfectly valid. can you describe exactly what your problem is?
I completely agree with you that the xml is valid when he searches for & and replaces with & You are right that the link is kind of misleading
I tested it and goes good if the incoming data contains & instead of &
To make your XML well formed, this is what available at this stage and I could think of. Or else get the Ampersand converted as & from source itself. This is an escape character for HTML docs.
Thanks for the response. It is accepting & but not & alone. I have used Data Process to do Search or Replace & with &.
However I am sending this same name "Hotel & Suites Arizona" to a message shape where i am generating another XML which is changing & to & again. This message shape is causing the whole issue.
I do not think just passing through message shape changes & to &. I guess something else is wrong in your message shape. Check whether you have added any custom string and passing the same to XML. Or else share a screen shot of the shapes involved
the solution using Data process shape with search(&) and replace(&) work perfectly for many customers.Is it passible to share process flow screen shots and sample data with which you are facing issue to process in Boomi?
What is the source of data and what is the target to end data?At which shape or step it is breaking?
Hi, if the input can be various kind of special character, like &, @, < , >, then we need to search and replace it for every character?
Generally, there is no need for custom escaping anywhere. Boomi will automatically handle any escaping when writing and reading xml documents (or json, etc).
The only time you may need to do custom escaping is if:
Hi James, thanks for reply, not sure should i continue to hijack this topic or should i create a new one.
We do notice that when SFDC(source) pass "&" inside the input, the document in Boomi showed "&"; and after the processes/mapping in Boomi, when it push to LDAP(target), the value automatic become "&".
Just want to confirm is it what you mean "Boomi will automatically handle any escaping when writing and reading xml documents" in your previous reply? Thanks.
It sounds like everything is working correctly, so i'm not sure i understand your question?
Sorry for causing any confusion, cause we perform the testing with multiple tools like SoapUI, postman, and also put the payload in Message Shape and run in test mode. We experience the mentioned issue which lead me to post here.
However, when we tested from Salesforce, we noticed the '&' become '&' from document in process reporting, which we kind a wondering why inconsistent behavior occur, perhaps we using the tools wrongly. Well, everything is working fine now. Thanks for the help.
Retrieving data ...