Exciting news… Version 1.9.1.0 of BizTalk Mapper Extensions UtilityPack for BizTalk Server 2013 R2 and 2013 is now available!
Here’s the changelog for this release:
- Updated Logical Functoids:
- The project has signed a strong name key, which resolved the issue “Unable to add BizTalk.Logical.Functoids.dll to the GAC (version 1.9.0.0)”. However, this is a false problem or a BizTalk Deployment Framework issue that always tries to put the functoids assemblies in the GAC. In reality, these functoids don’t need to be placed inside the GAC.
- Updated CRM Functoids:
- CRM Lookup Functoid: This functoid was updated. This functoid allows you to retrieve a value from a CRM lookup field. But now this functoid is also able to perform a lookup operation using two different approaches: Accessing the CRM database (read-only), for local CRM integration, or through the CRM web services if you want to avoid giving access to the database or if you have to integrate CRM online.
📝 One-Minute Brief
One-Minute Brief (TL;DR):
The new CRM Lookup Functoid
One of the biggest changes in this new version was made by Salvatore Pellitteri, who decided to update the previous CRM Lookup Functoid (also created by him) to add additional features.
This functoid is based on the previous one, which allows you to retrieve a value from a CRM lookup field. However, this new version of the functoid is able to perform a lookup operation using two different approaches:
- Accessing the CRM database (read-only) for local CRM integration.
- Through the CRM web services, if you want to avoid giving access to the database, or if you have to integrate CRM online.
Parameters
The functoid takes five mandatory input parameters:
- SSO Application Name: The connection parameters are stored inside SSO. Here, you have to specify the application name where you decide to store the settings. This allows you to integrate multiple CRM environments.
- CRM Guid Field Name: key field name of which you want to get the value.
- CRM Entity Name: CRM entity name on which the resolution will be performed.
- CRM Input Field Name: Imagine having a “code” as input, and you want to know the CRM physical key; in this attribute, you should specify the name of the “code” field.
- CRM Input Value: value from the source system to resolve.
The output of the functoid is a string. Example: 6erg5r-sdrf56-4dfgt5-6ty5r4-456trt 24
Installation
Create an SSO application.
SQL Server Lookup
Create the following SSO configuration parameters:
- CrmConnectionType: “sql”
- CrmDatabaseConnectionString: specify the CRM database connection string
Open SQL Server management console, connect to the CRM database, and execute the script under the CRMLookup.sql file in the project folder.
Local CRM web services lookup
Create the following SSO configuration parameters:
- CrmConnectionType: “ws”
- CrmUserName: specify a valid CRM username
- CrmUserDomain: specify a user’s active directory domain name
- CrmUserPassword: specify the user password
- CrmUri: specify the CRM web service URL (ex, http://MyCrmServer/MyCrmInstance/XRMServices/2011/Organization.svc)
CRM Online web services lookup
Create the following SSO configuration parameters:
- CrmConnectionType: “ws”
- CrmUserName: specify a valid CRM username (ex: harry@mydomain.onmicrosoft.com
- CrmUserPassword: specify the user password
- CrmUri: specify the CRM web service URL (ex, https://mydomain.crm4.dynamics.com/XRMServices/2011/OrganizationData.svc )
Download
THESE FUNCTOIDS ARE PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND.
You can download BizTalk Mapper Extensions UtilityPack from GitHub here:
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.
