none
Handle special characters xml file using CDATA RRS feed

  • Question

  • <ns0:Root xmlns:ns0="http://ProjReference.Schema1">
    
    <Name>Boygirl></Name>
    <City>Miami</City>
    <State>FL</State>
    <Country>USA</Country>
    <Data>Boy &  girl &> were the > best students</Data>
    </ns0:Root>
    

    I am having above xml coming from source system.The Data field will be receiving some special characters (which makes it as invalid xml).

    What is the best way to handle this scenario in BizTalk ?
    Create a custom pipeline component ? OR
    Using CDATA at the source before receiving to BizTalk 

    What would be best to approach ? what are the drawbacks. Please advise

    RH

    Tuesday, November 19, 2019 9:34 PM

Answers

  • Hi,

    The best approach is to tell the source system to at least send valid XML. You'll only get more problems trying to fix the invalid XML.

    Br,

    Leo


    Did my post help? Please use "Mark as answer" or "Propose as answer". Thank you!

    Wednesday, November 20, 2019 8:17 AM
  • Hi,

    The best approach is to tell the source system to at least send valid XML. You'll only get more problems trying to fix the invalid XML.

    Br,

    Leo


    That's what I told him in the other thread as well 

    Removing xml using Custom Pipeline component

    Those special characters need to be escaped as &lt; and &gt; by the system generating the XML.


    Wednesday, November 20, 2019 10:00 PM

All replies

  • Hi,

    The best approach is to tell the source system to at least send valid XML. You'll only get more problems trying to fix the invalid XML.

    Br,

    Leo


    Did my post help? Please use "Mark as answer" or "Propose as answer". Thank you!

    Wednesday, November 20, 2019 8:17 AM
  • Hi,

    The best approach is to tell the source system to at least send valid XML. You'll only get more problems trying to fix the invalid XML.

    Br,

    Leo


    That's what I told him in the other thread as well 

    Removing xml using Custom Pipeline component

    Those special characters need to be escaped as &lt; and &gt; by the system generating the XML.


    Wednesday, November 20, 2019 10:00 PM
  • Hi Colin,

    Glad we agree :)

    Br,

    Leo


    Did my post help? Please use "Mark as answer" or "Propose as answer". Thank you!

    Thursday, November 21, 2019 7:59 AM