Myself

I’m a SharePoint Solutions /SSIS /Biztalk/SQL/ASP.Net Developer currently working for Interpublic Group . I currently specialize in all the integration aspects of Biztalk,
implementing EAI solutions, In SharePoint dvwp, creating webparts, and creating things with jQuery. For 10+ years, I have developed software solutions that
add business value and create cost saving opportunities. I am very
experienced in BizTalk Server 2006/2009/2010/2013 and am consistently recognized by
others for exceeding expectations in the delivery of quality solutions.
Education

MS Software Engineering: Texas University

Technical Certifications

MCTS Biztalk 2006/ 2010

Jin Thakur

 

How to use distinguished fields and promoted properties in a BizTalk Server project

Admin:
How to use distinguished fields and promoted properties in a BizTalk Server project?

When you use distinguished fields and promoted properties, consider the following points:

Use distinguished fields when you want to make decisions or to manipulate data in an orchestration. The pipeline disassembler will insert a Written property into the message context for items that are marked as a distinguished field.
Use promoted properties as criteria for message routing. However, notice that promoted properties are also available in an orchestration. The pipeline disassembler will insert a Promoted property into the message context for items that are marked as a promoted property.
Promoted properties are limited to 256 characters for performance reasons. For example, promoted properties are limited to 256 characters to improve performance in comparison operations and in storage operations.
Written properties do not have a size limit. However, large values that are written into the message context must still be processed by BizTalk Server. Therefore, performance may be affected.
A promoted property may not be available as a promoted property after you write a value into the message context. This situation can occur if the value that you write into the message context has the same name and namespace that was used to promote the property.
Properties that have a null value are not permitted in the message context. Therefore, if a null value is written into the message context, this value will be deleted.

New WCF schema and other schema with namespace does not work in same way as it was in Biztalk 2009

New WCF schema and other schema with namespace does not work in same way as it was in Biztalk 2009

//CALLINGCARD or ./CALLINGCARD does not work in XSLT foreach loop

We have to add Local name for element and attributes

example "*[local-name()='CALLINGCARD' and namespace-uri()='http://Microsoft.LobServices.Sap/2007/03/Rfc/']"

New WCF schema and other schema with namespace does not work in same way as it was in Biztalk 2009
8-)8-)8-)8-)|-)|-)(bo)(bo)(bo)(bo)(bo)(bo)
Previous code

<xsl:element name="ItemCollection">
<xsl:for-each select="//*[local-name()='Root' and namespace-uri()='http://schemas.microsoft.com/BizTalk/2003/aggschema']/*[local-name()='InputMessagePart_0' and namespace-uri()='']/*[local-name()='TESTRFCMESSAGE' and namespace-uri()='http://Microsoft.LobServices.Sap/2007/03/Rfc/']">

<xsl:element name="Item">

<xsl:element name="Value">
<xsl:attribute name="CssClass">table_item_info</xsl:attribute>
<xsl:attribute name="Text" >
<xsl:value-of select="//CALLINGCARD"/>
</xsl:attribute>
</xsl:element>

<xsl:element name="Value">
<xsl:attribute name="CssClass">table_item_info</xsl:attribute>
<xsl:attribute name="Text" >
<xsl:value-of select="//RESULT"/>
</xsl:attribute>
</xsl:element>

</xsl:element>
</xsl:for-each>