BizTalk Mapper Extensions UtilityPack for BizTalk Server 2013 Updated to v1.8.0.0

  • Sandro Pereira
  • Apr 7, 2015
  • 5 min read

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 about first… This project has 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.
  • Salvatore Pellitteri. He is a Developer Team Manager at Microsys Srl. He works on integration application projects using BizTalk Server and on business intelligence projects using the SQL Server platform. He has worked with BizTalk Server since the first version and has worked on 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.

📝 One-Minute Brief

BizTalk Mapper Extensions UtilityPack v1.8.0.0 (for BizTalk Server 2013) is out, adding 7 new functoids—including a set of Dynamics CRM “Map Helper” functoids, a native XPath functoid, and a SharePoint 2013 Document Set functoid—plus a shout-out to the two new contributors behind these additions.

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 to 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 the CRM Lookup functoid, where you first find the entity guid and then use the result to map to the destination schema.

MSCRM Map Helper Money Functoid

Use this functoid when you want to map the 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 to map the 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 to 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 the inline XSLT Call template script functoid.

MSCRM requires that different data types be specified in a different way. For this reason, we provide a set of functoid each specific data type.

Use this functoids in two steps:

  • First Step:
MSCRM Map Helper Functoids
  • Second Step:
MSCRM Map Helper Functoids

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, 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.

XPath Custom 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 be created.

Comment: A custom content-type of type documentset needs to be available in SharePoint.

Download

You can download the source code and application binaries from GitHub:

Hope you find this helpful! If you liked the content or found it useful and would like to support me in writing more, consider buying (or helping to buy) a Star Wars Lego set for my son. 

Thanks for Buying me a coffe
Author: Sandro Pereira

Sandro Pereira lives in Portugal and works as a consultant at DevScope. In the past years, he has been working on implementing Integration scenarios both on-premises and cloud for various clients, each with different scenarios from a technical point of view, size, and criticality, using Microsoft Azure, Microsoft BizTalk Server and different technologies like AS2, EDI, RosettaNet, SAP, TIBCO etc. He is a regular blogger, international speaker, and technical reviewer of several BizTalk books all focused on Integration. He is also the author of the book “BizTalk Mapping Patterns & Best Practices”. He has been awarded MVP since 2011 for his contributions to the integration community.

1 thought on “BizTalk Mapper Extensions UtilityPack for BizTalk Server 2013 Updated to v1.8.0.0”

Leave a Reply

Your email address will not be published. Required fields are marked *

The Ultimate Cloud
Management Platform for Azure

Supercharge your Azure Cost Saving

Learn More
Turbo360 Widget

Back to Top