CDATA in XML feed
Good afternoon.
We encountered the following problem while working with XML feed.
???? The gist:
We receive an incoming XML feed containing <![CDATA[...]]> blocks, most commonly found in property listings. This feed is processed in our system, and then we generate our own output feed, which is sent to the Kyero portal.
???? Problem:
The Kyero portal prohibits the use of CDATA (as well as HTML tags) in text fields, especially <description>. As a result, our feed is rejected when imported to their side.
✅ Question:
Is it possible to remove the CDATA wrapper at the output feed generation stage in our system and pass the content as plain text? It is important that:
Special characters (<, >, &) were preserved in correct XML form (for example, replaced with <, >, &)
The XML structure was not violated
Original question is available on version: ru
We encountered the following problem while working with XML feed.
???? The gist:
We receive an incoming XML feed containing <![CDATA[...]]> blocks, most commonly found in property listings. This feed is processed in our system, and then we generate our own output feed, which is sent to the Kyero portal.
???? Problem:
The Kyero portal prohibits the use of CDATA (as well as HTML tags) in text fields, especially <description>. As a result, our feed is rejected when imported to their side.
✅ Question:
Is it possible to remove the CDATA wrapper at the output feed generation stage in our system and pass the content as plain text? It is important that:
Special characters (<, >, &) were preserved in correct XML form (for example, replaced with <, >, &)
The XML structure was not violated
Answers:
The box by default does not set CDATA as far as I know for files. In order to ignore some unwanted characters, you can, in theory, make auto-replacement in the action settings. Give a link to the box and an example of the action settings that you are currently generating a file with, so that you can take a closer look and understand what needs to be done there.
29.05.2025, 14:31
Original comment available on version: ru
Please join the conversation. If you have something to say - please write a comment. You will need a mobile phone and an SMS code for identification to enter.
Log in and comment
Copyright © OneBox 2025
