Hello, every time I test the map I get the following error:
Inline XSLT in Mapper output validation error: The "Coverage" element is not
declared. The "CoverageCode" element is not declared.

Note:  The map validates without errors, but not when I test it.  I am using
a Scripting Functoid in the Map with an Inline XSLT Call Template. I am usin
g
BizTalk Server 2004.

Does anyone know why this is happening?

Here is the example of my inline XSLT:
<xsl:template name="OrderCoverageCodeXSLT">
<xsl:param name="param1"/>
<xsl:param name="param2"/>
<xsl:element name="Coverage">
<xsl:element name="CoverageCode"><xsl:value-of select="$param1"
/></xsl:element>
</xsl:element>
<xsl:element name="Coverage">
<xsl:element name="CoverageCode"><xsl:value-of select="$param2"
/></xsl:element>
</xsl:element>
</xsl:template>

Thanks in advance for your help.
--
mj

[ Post a follow-up to this message ]

Hi mj,

Could you send me with the schema and mapping files to let me take a
look?

v-wzhang@online.microsoft.com (please remove online.)

Thanks.

Best regards,

WenJun Zhang
Microsoft Online Partner Support

This posting is provided "AS IS" with no warranties, and confers no
rights.

[ Post a follow-up to this message ]

Hi Marci,

I've figured the cause of the error you met. If you generated a valid
instance of target schema OSITracCommon, you will see all its
elements include the namespace prefix, e.g: <ns0:AdditionalComment> .
However the XSLT template you used in the map doesn't populate the
elements with the namespace prefix.

<xsl:element name="Note">
<xsl:element name="AdditionalComment"><xsl:value-of select="$param6"
/></xsl:element>
</xsl:element>

So the schema validator looks for <ns0:AdditionalComment> and reports
<AdditionalComment> is not declared.

To resolve the problem, you can simply set Attribute FormDefault and
Element FormDefault to 'Unqualified' in OSITracCommon.xsd's <schema>
node property. Then the namespace prefix isn't enforced which will
not impact the validity of XML instance.

By the way, I still see some data type mismatching errors after the
'not declared' one get fixed. You may do some further checking on it.

Thanks.

Best regards,

WenJun Zhang
Microsoft Online Partner Support

This posting is provided "AS IS" with no warranties, and confers no
rights.

[ Post a follow-up to this message ]