I have below xml file
<htmlResponses>
<resultSet></resultSet>
<referencePoint></referencePoint>
<htmlResponse></htmlResponse>
<htmlResponse></htmlResponse>
<htmlResponse></htmlResponse>
</htmlResponses>
And I want to get node "htmlResponse" collection in a xsl variable so I can loop through it by using XSLT.
Can anyone guide me how can I achieve this?
Agreed with Hobbes, but you could do this:
<xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform">
<xsl:variable name="responses" select="//htmlResponse"/>
<xsl:template match="/">
... do something ...
<xsl:for-each select="$responses/*">
...
</xsl:for-each>
</xsl:template>
</xsl:stylesheet>
The only use case I can think of where this makes sense is if you have a lot of data, and wish to build your node set using xsl:key and then reuse that node set multiple times.
Related
I'm trying to split an incoming message in the following form:
<Items>
<BatchID>123</BatchID>
<Item>...</Item>
<Item>...</Item>
<Item>...</Item>
</Items>
I've a pipeline with a XML disassembler which takes the Items schema and outputs the Item schema. On the Items schema, the Envelope property is set to true, and the "Body XPath" property points to the Items element.
However, when I try to process a file, I get the error: Finding the document specification by message type "BatchID" failed. Verify the schema deployed properly., presumably because it's expect only Item elements, and it doesn't know what to do with the BatchID element.
If I make the BatchID an attribute on the Items element (like a sensible person would have), everything works fine. Unfortunately, I'm stuck with the layout.
At this time, I do not care what is the value of BatchID.
How do I get it to split the message?
AFAIK the Xml disassembler always extracts all child nodes of the specified body_xpath element - it would have been a nice feature to be able to specify Item Xpath instead :(.
You can workaround this limitation by either:
Creating a schema for the undesirable <BatchID> element, and then just eat instances of it, e.g. creating a subscribing send port using TomasR's Null Adapter
or, Transform the envelope in a map on the receive port, before the envelope is debatched, where the transform strips out the unwanted Batch element
The following XSLT should do the trick:
<?xml version="1.0" encoding="utf-8"?>
<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" xmlns:msxsl="urn:schemas-microsoft-com:xslt" xmlns:var="http://schemas.microsoft.com/BizTalk/2003/var" exclude-result-prefixes="msxsl var" version="1.0" xmlns:ns0="http://BizTalk_Server_Project3.Envelope">
<xsl:output omit-xml-declaration="yes" method="xml" version="1.0" />
<xsl:template match="/">
<xsl:apply-templates select="/ns0:Items" />
</xsl:template>
<xsl:template match="/ns0:Items">
<ns0:Items>
<!--i.e. Copy all Item elements and discard the Batch elements-->
<xsl:copy-of select="ns0:Item"/>
</ns0:Items>
</xsl:template>
</xsl:stylesheet>
See here on how to convert a btm from a visual map to xslt
Using Biztalk 2010 I have a incoming message with this structure:
<xml><blocks>
<block id="level">
<message id="code">100</message>
<message id="description">Some description</message>
</block>
<block id="level">
<message id="code">101</message>
<message id="description">More description</message>
</block>
</blocks>
<blocks>
<block id="change">
<message id="table">1</message>
<message id="oldvalue">100</message>
<message id="newvalue">101</message>
</block>
</blocks>
</xml>
I need to map the above to this structure:
<terms>
<termItem>
<code>100</code>
<description>Some description</description>
<deleted>false</deleted>
</termItem>
<termItem>
.....and so on with values from the above xml file, except that the item from the "change" block should be added as a new record to output, so the total output will be 3 items (<block>).
The map view is like this:
I need some help in choosing the right combination of either functoids to use, or maybe another approach to solve this challenge.
I'm able to either choose all blocks with the "level" value and filter out the "change" block, but unable to make a combination of the two.
Any hints, suggestions are very welcome.
Thanks
There seems to be more than meets the eye
The incoming xml seems to be nested (as per the schema in the visual mapper), so the example input xml structure might not quite be right?
Also, it might be that the schema on the RHS is debatched, i.e. one PaymentTerms message per company id, so unless you only need to map the first Company, you will need to create a wrapper schema for all mapped companies, with an arbitrary root node, and then debatch them before sending.
That said, it is relatively straightforward to get the general structure of the output by using a custom xslt instead of the visual mapper. I've assumed the RHS schema on your diagram for the real output schema (not your terms example).
<xsl:stylesheet version="1.0"
xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
exclude-result-prefixes="xsl xsi">
<xsl:output method="xml" indent="yes" />
<xsl:strip-space elements="*" />
<!--Outer template-->
<xsl:template match="/">
<PaymentTerms CompanyCode="Unsure">
<xsl:apply-templates />
</PaymentTerms>
</xsl:template>
<!--Root blocks only-->
<xsl:template match="block[#id='level']">
<PaymentTerm>
<Code>
<xsl:value-of select="message[#id='code']/text()"/>
</Code>
<Description>
<xsl:value-of select="message[#id='description']/text()"/>
</Description>
<Deleted>
<!--No idea how you want this populated-->
<xsl:value-of select="'false'"/>
</Deleted>
</PaymentTerm>
<xsl:apply-templates select="blocks/block"></xsl:apply-templates>
</xsl:template>
<!--Nested blocks only-->
<xsl:template match="block[#id='change']">
<PaymentTerm>
<Code>
NestedCode
</Code>
<Description>
NestedDescription
</Description>
<Deleted>
NestedDeleted
</Deleted>
</PaymentTerm>
</xsl:template>
</xsl:stylesheet>
You didn't provide much info on how the nested blocks are to be mapped, so I've provided placeholders in the meantime.
HTH!
My incoming XML has the following
<ROOT-PARENT xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:noNamespaceSchemaLocation="ASR_V3.0.1_proposed.xsd">
I am using a Inline XSLT in Scripting Functoid in BizTalk 2010
I want to navigate one of the child nodes but I am unable to get the values. Do i need to
My XSLT looks like
<EXTERNALTAG xsi:noNamespaceSchemaLocation="ASR_V3.0.1_proposed.xsd">
<xsl:for-each select ="//MILESTONES/MILESTONE">
<P><xsl:value-of select="."/></P>
</xsl:for-each>
</EXTERNALTAG>
The above doesn't seem to work. Any idea what i need to do in order to take care of the
xsi:noNamespaceSchemaLocation
Thanks in advance
Karthik
OK. If my XSLT looks like this
<EXTERNALTAG> <xsl:for-each select ="//MILESTONES/MILESTONE"> <P><xsl:value-of select="."/></P> </xsl:for-each> </EXTERNALTAG>
everything is working fine
Thanks
Is there anyway in a BizTalk map to force destination elements to be created when the source elements don't exist without using an xslt call template?
I'm mapping parent/child xml to a wcf-sql adapter generated schema that has table-valued parameters for stored proc parameters.
So my source xml is:
<Category>
<CategoryId>1</CategoryId>
<CategoryName>Test</CategoryName>
</Category>
and/or a Category with Media
<Category>
<CategoryId>1</CategoryId>
<CategoryName>Test</CategoryName>
<Media>
<Medium>
<MediumId>1</MediumId>
<MediumName>test.jpg</MediumName>
</Medium>
</Media>
</Category>
The schema for the TypedProcedure is something like:
<ImportCategoryRequest>
<Category>
<CategoryId>1</CategoryId>
<CategoryName>Test</CategoryName>
</Category>
<Media>
<Medium>
<MediumId>1</MediumId>
<MediumName>test.jpg</MediumName>
</Medium>
</Media>
</ImportCategoryRequest>
So it doesn't like it when is all that shows up in the destination XML. Instead of passing null for a table-valued parameter it wants at least 1 row and to pass null values for the columns in the tvp. I can create the dummy xml with a xslt call-template but I'd like to avoid that.
The BizTalk mapper seems to use <xsl:for-each> and as a result won't generate an output element if there is no input.
But using xslt is really easy - see here how to scrape the xslt out of your existing map (and just remove the escaping around double quotes and slashes), and to change the map to custom XSLT.
The bit you need to change is around the Media is something like:
<xsl:choose>
<xsl:when test="count(ns0:Media)!=0">
<!-- Copy the mapper generated XSLT in the for each here-->
<xsl:foreach >
</xsl:for-each>
</xsl:when>
<xsl:otherwise>
<Media>
<Medium>
<MediumId>1</MediumId>
<MediumName>test.jpg</MediumName>
</Medium>
</Media>
</xsl:otherwise>
</xsl:choose>
Background:
I have an old web CMS that stored content in XML files, one XML file per page. I am in the process of importing content from that CMS into a new one, and I know I'm going to need to massage the existing XML in order for the import process to work properly.
Existing XML:
<page>
<audience1>true</audience>
<audience2>false</audience>
<audience3>true</audience>
<audience4>false</audience>
<audience5>true</audience>
</page>
Desired XML:
<page>
<audience1>true</audience>
<audience2>false</audience>
<audience3>true</audience>
<audience4>false</audience>
<audience5>true</audience>
<audiences>1,3,5</audiences>
</page>
Question:
The desired XML adds the node, with a comma-delimited list of the other nodes that have a "true" value. I need to achieve the desired XML for several files, so what is the best way to accomplish this? Some of my ideas:
Use a text editor with a regex find/replace. But what expression? I wouldn't even know where to begin.
Use a programming language like ASP.NET to parse the files and append the desired node. Again, not sure where to begin here as my .NET skills are only average.
Suggestions?
I would probably use the XmlDocument class in .net, but that's just me because I've never been that fond of regexs.
You could then use XPath expressions to pull out the child nodes of each page node, evaluate them, and append a new node at the end of the page children, save the XmlDocument when you are done.
Xsl is an option too, but the initial learning curve is a bit painful.
There's probably a more elegant way with a regex, but if you are only running it once, it only matters that it works.
I would likely use an XSLT stylesheet to solve this problem. I built the following stylesheet to be a little bit generic that exactly what you asked for, but it could easily be modified to give you the exact output you had specified if you truly need that exact output.
<?xml version="1.0" encoding="utf-8"?>
<xsl:stylesheet version="1.0"
xmlns:xsl="http://www.w3.org/1999/XSL/Transform">
<xsl:template match="/">
<xsl:apply-templates select="/*"/>
</xsl:template>
<xsl:template match="/*">
<xsl:copy>
<xsl:copy-of select="*"/>
<xsl:element name="nodes">
<xsl:apply-templates select="*[normalize-space(.) = 'true']"/>
</xsl:element>
</xsl:copy>
</xsl:template>
<xsl:template match="/*/*">
<xsl:value-of select="concat(',', local-name())"/>
</xsl:template>
<xsl:template match="/*/*[1]">
<xsl:value-of select="local-name()"/>
</xsl:template>
</xsl:stylesheet>
This XSLT's output would be:
<page>
<audience1>
true
</audience1>
<audience2>
false
</audience2>
<audience3>
true
</audience3>
<audience4>
false
</audience4>
<audience5>
true
</audience5>
<nodes>audience1,audience3,audience5</nodes>
</page>
XSLT would be a good fit for this because you can use from almost any programming language you want or you could use Visual Studio to apply the template. There are also many free tools out there that you could use to apply the transformations.