I'm trying to use the XSLT Visualizer with a query result that contains an xml column type. The relevant part of the table definition is:

    [CountryCode] [char](2) NOT NULL,
    [PostCode] [nvarchar](20) NULL,
    [Region] [nvarchar](25) NULL,
    [Municipality] [nvarchar](25) NULL,
    [DeliveryAddress] [xml] NULL,

The 'Show XML Source' button on the settings page shows the following:

<DocumentElement>
  <QueryResults>
    <CountryCode>US</CountryCode>
    <PostCode>38117</PostCode>
    <Region>TN</Region>
    <Municipality>Memphis</Municipality>
    <DeliveryAddress>&lt;Address&gt;&lt;Line&gt;c/o John Doe&lt;/Line&gt;&lt;Line&gt;123 Main St&lt;/Line&gt;&lt;Unit&gt;4th Floor&lt;/Unit&gt;&lt;City&gt;Memphis&lt;/City&gt;&lt;State&gt;TN&lt;/State&gt;&lt;PostalCode&gt;38117&lt;/PostalCode&gt;&lt;/Address&gt;</DeliveryAddress>
  </QueryResults>
</DocumentElement>

I tried using the HTML Decode converter on DeliveryAddress but it didn't help.

I spent a little time looking at the source code but I'm going to need to get the source installed so I can step through it in VS it or generate some trace output to figure this out. Before doing that I thought I'd ask for some thoughts on what's causing this and potential workarounds.

• It appears to be the DataTable.WriteXml method that's encoding the value of that column.
• Even with the htmldecode converter there is a single child node of DeliveryAddress that is a text() node.
• I tried msxml:node-set() in the xslt stylesheet but it just returns a text node. It doesn't parse and load it as an XML document or fragment.
• I tried adding script to the stylesheet to actually load it into an XPathDocument and return an XPathNodeIterator but I get a script not allowed error because the Reports module isn't enabling script execution for the transformation.

Any thoughts on how I should proceed?

Thanks, Paul

Have you clicked on the "Show XML Source" link below your query on Settings page for the module? The module wraps your query results in a top level element named DocumentElement and in that each row is in an element named QueryResults.

You don't need to specify a XML namespace and the .Net Type setting unless you are using an XSLT extenstion object (calling compiled code from within the XSLT stylesheet.) I'm not familiar with Dreamweaver but perhaps there are built in extension object in Dreamweaver that your XSLT is using. If you are, you would have namespaces defined in you stylesheet element. For example, and unrealated to DNN, I use a command line XLST transformer that has all of the EXLT.org extensions built in. So, to use those built in string manipulation extension objects I define a namespace xmlns:str="http://exslt.org/strings" then I can use something like str:replace( $url, '/', '/​' ). If I were to use that replace function in an XSLT file in the DNN Reports module, I would get a compile error.

The other possibility is that Dreamweaver supports XPath 2.0, which .Net does not. So any XPath 2.0 functions would throw a compile error.

Dreamweaver probably declares the nbsp entity for you. You could use &#160; (the decimal code for non-breaking space) instead or define the entity yourself. To define your own entities put the following after the xml declaration and before your stylesheet element (the example has several entities that aren't defined by default):

<!DOCTYPE xsl:stylesheet [
 <!ENTITY nbsp "&#160;">
 <!ENTITY pound "&#163;">
 <!ENTITY yen "&#165;">
 <!ENTITY copy "&#169;">
 <!ENTITY laquo "&#171;">
 <!ENTITY reg "&#174;">
 <!ENTITY middot "&#183;">
 <!ENTITY raquo "&#187;">
 <!ENTITY bull "&#8226;">
 <!ENTITY mdash "&#8212;">
 <!ENTITY ldquo "&#8220;">
 <!ENTITY rdquo "&#8221;">
 <!ENTITY euro "&#8364;">
 <!ENTITY trade "&#8482;">
]>