Result Xslt Not As Expected フォローする

Legacy Poster



I'm using commander to translate a third party xml file to btxml, this works fine when I create a btxml file from my xml file and execute in Bartender. But when I use commander the tranformation is incomplete. My xsl content:

<xsl:transform version="1.0" 

<!-- suppress default template outputting all text -->
<xsl:template match="text()"/>

<!-- main template -->
<xsl:template match="models:WMSPurchaseOrderReceive02Model">
	<XMLScript Version="2.0">
		<Command Name="Job 1">
				<NamedSubString Name="itemNumber"><Value><xsl:value-of select="models:_x003C_ItemNumber_x003E_k__BackingField"/></Value></NamedSubString> 

Which results in:

<?xml version="1.0"?>
<XMLScript xmlns:models="" xmlns:label="" Version="2.0">
	<Command Name="Job 1">
			<NamedSubString Name="itemNumber">

Executing this from Bartender gives me the right result, a label with 900110 where it should. However, if I do this from commander it indicates the transformation was correct, but the log does not mention the NamedSubString and the label does not contain the 900110. The log result is this:

Command Handler: testHandler - C:\PROGRA~2\Seagull\BARTEN~1\bartend.exe /XMLScript=<?xml version="1.0"?><XMLScript Version="2.0" xmlns:models="" xmlns:label=""><Command Name="Job 1"><Print><Format>\\share\test.btw</Format></Print></Command></XMLScript>

No mention of the NamedSubstring.


Is this normal behaviour, or am I missing something?


Thank you for your help




No idea how, but now it works. After adding a command to write the filtered trigger content to a file I could see the NamedSubstring, and the label contained the data.