Important Notice from AspDotNetStorefront
It is with dismay that we report that we have been forced, through the action of hackers, to shut off write-access to this forum. We are keen to leave the wealth of material available to you for research. We have opened a new forum from which our community of users can seek help, support and advice from us and from each other. To post a new question to our community, please visit: http://forums.vortx.com
Results 1 to 2 of 2

Thread: WSI ExtensionData Imported and XmlEncoded - how are you using this?

  1. #1
    mbertulli is offline Senior Member
    Join Date
    Aug 2008
    Posts
    243

    Default WSI ExtensionData Imported and XmlEncoded - how are you using this?

    Hey Guys,

    Out of curiosity, I'm wondering how others are working with storing XML in Product.ExtensionData via WSI. When we upload product data via WSI that contains XML in the ExtensionData field, we end up with encoded xml in the database. This is causing some issues on using the ExtensionData xml in our XMlPackages.

    Basically, WSI is doing an XmlEncode() on the passed in xml string. We end up with the following in the database:

    <Title>Inductive Preaching</Title>
    Is there a nice way to work with this now in XMLPackages? Or do you have to re-write the wsi code to not do the XmlEncode()?
    Matthew Bertulli
    Demac Media
    mbertulli@demacmedia.com
    Custom Web Design & E-Commerce Development
    AspDotNetStoreFront Platinum DevNet Partner
    ----

    Custom Skinning & Design
    Web Services Integration
    Custom Reporting
    Salesforce.com eCommerce AspDotNetStoreFront Integration

  2. #2
    ASPAlfred is offline Senior Member
    Join Date
    Nov 2007
    Posts
    2,244

    Default

    It looks like you need to use CDATA so that it's not parsed by the XML parser.

    e.g.
    Code:
    <![CDATA[<Title>Inductive Preaching</Title>]]>
    With the example below, everything inside the CDATA section is ignored by the parser.