Exciting news… Version 1.8.0.0 of BizTalk Mapper Extensions UtilityPack for BizTalk Server 2013 is now available!
But before talking about the changelog of this version there is another subject that I want to talk first… This project as two new members that was responsible for all the new functionalities available in this version:
- Martijn Schiedon, Integration architect at ValueBlue (http://www.valueblue.nl) and a Dutch BizTalk community member.
- And Salvatore Pellitteri. He is Developer Team Manager in Microsys Srl. He works on integration application projects using BizTalk Server and on business intelligence projects using SQL Server platform. He works with BizTalk Server since the first version and has worked in many big integration projects with several Italian enterprise organizations using many technologies like SAP, Oracle, SQL Server, AS400, J.D. Edwards and HL7. Salvatore has his own blog https://pellitterisbiztalkblog.wordpress.com/ on which he shares his experiences.
Here’s the changelog for this release:
- Seven new functoids:
- MSCRM Map Helper Base Types Functoid
- MSCRM Map Helper Guid Functoid
- MSCRM Map Helper Money Functoid
- MSCRM Map Helper Option Value Functoid
- MSCRM Map Helper References Functoid
- XPath Functoid
- Add SharePoint 2013 Document Set Functoid
What’s new in this version?
Although BizTalk Server provides many functoids to support a range of diverse operations when working with conditional mapping, we are limited to the number of existing operations or otherwise have to use custom XSLT.
MSCRM Map Helper Base Types Functoid
Use this functoid when you want map CRM base data types such as “xs:string”, “xs:int” and so on.
Parameters
The functoid takes three mandatory input parameters:
- Source Field: Link from source schema field value.
- Target Field Name: CRM target field name.
- Target Field Type: CRM target field type (Example: “xs:dateTime”).
The output of this functoid should be linked to:
- “/<Schema>/<CRM_Operation>/entity/Attributes/KeyValuePairOfstringanyType/key”.
MSCRM Map Helper Guid Functoid
Use this functoid when you want map CRM guid type.
Parameters
The functoid takes two mandatory input parameters:
- Source Field: Link from source schema field value.
- Target Field Name: CRM target field name
The output of this functoid should be linked to:
- “/<Schema>/<CRM_Operation>/entity/Attributes/KeyValuePairOfstringanyType/key”.
You may use this functoid in combination with CRM Lookup functoid, where first find for entity guid and then use the result to map to the destination schema.
MSCRM Map Helper Money Functoid
Use this functoid when you want map CRM money type.
Parameters
The functoid takes two mandatory input parameters:
- Source Field: Link from source schema field value.
- Target Field Name: CRM target field name.
The output of this functoid should be linked to:
- “/<Schema>/<CRM_Operation>/entity/Attributes/KeyValuePairOfstringanyType/key”.
MSCRM Map Helper Option Value Functoid
Use this functoid when you want map CRM option value type.
Parameters
The functoid takes two mandatory input parameters:
- Source Field: Link from source schema field value.
- Target Field Name: CRM target field name.
The output of this functoid should be linked to:
- “/<Schema>/<CRM_Operation>/entity/Attributes/KeyValuePairOfstringanyType/key”.
MSCRM Map Helper References Functoid
Use this functoid when you want map CRM reference type.
Parameters
The functoid takes three mandatory input parameters:
- Source Field: Link from source schema field value.
- Target Field Name: CRM target field name.
- Entity Name: CRM referenced entity.
The output of this functoid should be linked to:
- “/<Schema>/<CRM_Operation>/entity/Attributes/KeyValuePairOfstringanyType/key”.
MSCRM Map Helper Functoids
These functoids allow you to Integrate Directly with the Dynamics CRM SOAP API, avoiding the use of inline XSLT Call template script functoid.
MSCRM requires that different data types are specified in a different way. For this reason, we provide a set of functoid each for the specific data type.
Use this functoids in two steps:
First Step

Second Step
XPath Functoid
This functoid natively integrates custom XPath queries in the BizTalk mapper. This unique functoid which is a powerful competitor to the ScripterFunctoid or a custom XSLT stylesheet and mixes exceptionally well with other functoids.
Parameters
The functoid takes one mandatory input parameter and one optional parameter:
- The first parameter specifies an absolute or relative XPath expression, which becomes a native part of the generated XSLT.
- The (optional) second parameter is a link to the source tree node that becomes the (looping) context for the XPath expression.
This defines the current context node for the XPath expression and allows the use of relative XPath expressions. Additionally, the mapper will generate a looping construct for that linked node where appropriate.
The functoid output can be linked to a destination schema node or serve as input to other functoids.

Add SharePoint 2013 Document Set Functoid
Creates a Document Set in an existing SharePoint 2013 List. It is a requirement that the SharePoint list contains a custom content-type of type document set.
Parameters
The following parameters are required:
- string siteUrl = SharePoint Site Url
- string listName = SharePoint List Name containing the custom content-type Document Set
- string docSetContentTypeName = Document Set Content Type name
- string newDocSetName=Name of the to document set to created
Comment: An custom content-type of type documentset needs to be available in SharePoint.
Download
You can download Source Code and Application Binaries here:BizTalk Mapper Extensions UtilityPack
GitHub
Reblogged this on Salvatore Pellitteri Biztalk Blog.