Microsoft Dynamics CRM Connector

Select

Latest version: 2.9.0

The Microsoft Dynamics Customer Relationship Management (CRM) connector lets you access Microsoft Dynamics CRM’s SOAP Organization Service. You can add this connector to an Anypoint Studio flow.

Release Notes: Microsoft Dynamics CRM Connector Release Notes
Technical Reference: MS Dynamics CRM Connector Technical Reference
Samples: dynamics-crm-connector-samples.zip

Overview

This connector lets you perform the following operations:

Create, update, and delete records
Retrieve a single record or query multiple records
Associate and disassociate records
Execute a request message

This connector supports these Microsoft Dynamics CRM versions:

Microsoft Dynamics CRM 2016 (on-premise)
Microsoft Dynamics CRM 2015 (on-premise)
Microsoft Dynamics CRM 2013 (on-premise)
Microsoft Dynamics CRM 2011 (on-premise)
Microsoft Dynamics CRM Online (8.0, 8.1, 8.2)

Configuring the connector requires minimal parameters except for advanced use:

Username and password for users granted access to CRM
Organization Service URL - usually in the format: https://mulesoft03.api.crm.dynamics.com/XRMServices/2011/Organization.svc

Installing and Configuring

Install the Java Cryptography Extensions (JCE) package before installing the connector.
Download JCE for Java 7 from Oracle’s Java 7 JCE Download site.
Download JCE for Java 8 from Oracle’s Java 8 JCE Download site.
In Anypoint Studio, click the Exchange icon in the Studio taskbar.
Click Login in Anypoint Exchange.
Search for the connector and click Install.
Follow the prompts to install the connector.

When Studio has an update, a message displays in the lower right corner, which you can click to install the update.

Configuring the Connector

Step 1: Create a New Mule Project

To configure:

In Anypoint Studio, click File > New > Mule Project.
Specify a Project Name and click Finish.

Step 2: Configure the Global Element

Configure the connector as a Microsoft Dynamics CRM instance:

Click the Global Elements tab and click Create.
In the Search field, type crm, click Microsoft Dynamics CRM, and click OK.
Click a connection strategy for authentication (for example, Microsoft Dynamics CRM: Kerberos Connection):
Specify a Username and Password.
Specify a Organization Service URL for accessing the CRM system. Click OK.

For example: https://{siteUrl}/XRMServices/2011/Organization.svc
Click Test Connection to ensure that the connection works correctly.
After the connection succeeds, click OK.

Creating a Mule Flow

To create a flow:

Click the Message Flow tab.
In the Search field, type http, and drag the HTTP connector to the canvas.
In the Search field, type crm, and drag the Microsoft Dynamics CRM connector to the canvas next to the HTTP connector.
In the Search field, type json, and drag the Object to JSON transformer to the canvas next to the connector. You can use the default values in this transformer.

The flow appears as:

To configure the flow:

Double-click the HTTP connector and click the green plus + sign to the right of Connector Configuration:
Set localhost, port 8081, and the Path to query:
Double-click Microsoft Dynamics CRM.
Click the green plus symbol + to the right of Connector Configuration:
Select the connection strategy for authenticating your CRM instance.
Specify your access to the CRM server: Username, Password, and Organization Service URL.
Click OK - See CRM Authentication for information on each authentication scheme.
For Operation, click Retrieve multiple by query. Note: This option only appears if you were able to successfully contact the CRM server.
For Query Language, click DataSense Query Language. Note: The Query section only appears for a query Operation.
Click Query Builder.
In the Query Builder window:
1. In Types, click account.
2. In Fields, click accountid, accountnumber, and name.
3. In Order By, click name.
4. In Direction, click DESCENDING.
5. Click OK.

Running a Flow

In Package Explorer, right click your project’s name, and click Run As > Mule Application.

Check the console to see when the application starts. You should see a message such as this example if no errors occur:

++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+ Started app 'crm-demo'                                   +
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Open a browser and visit http://localhost:8081/query

The list of accounts display in descending order by name and in JSON format (results vary according to your CRM instance). For example:

[{"name":"Alpine Ski House (sample)","accountnumber":"ABCO9M32","accountid":"f5a917b4-7e06-e411-82a5-6c3be5a8ad64"},
{"name":"Adventure Works (sample)","accountnumber":"ABC28UU7","accountid":"eba917b4-7e06-e411-82a5-6c3be5a8ad64"}]

CRM Authentication

Authentication Schemes

The Microsoft Dynamics CRM connector supports different authentication schemes based on the Microsoft Dynamics CRM that is accessed.

Supported authentication schemes for Microsoft Dynamics CRM on premise:

Windows Authentication - Kerberos
Windows Authentication – NTLM (requires Anypoint Gateway for Windows)
Claims-based Authentication

Supported authentication schemes for Microsoft Dynamics CRM online:

Live ID
Office 365

Advanced Kerberos Authentication

The preferred method of configuring the connector for Kerberos authentication is to leverage auto-configuration. The prerequisites for automatically detecting Kerberos configuration settings to work are:

Mule ESB server joined to the same domain as the CRM instance
AD Domain Controller is accessible from the Mule ESB server

In case the Kerberos configuration settings cannot be automatically detected, you can set the following parameters manually:

SPN: The Service Principal Name can usually be automatically discovered from the Organization Service’s WSDL. If the SPN cannot be discovered automatically, the value has to be set in the connector’s connection configuration property SPN. The SPN usually looks like host/SERVER-NAME.MYREALM.COM.

If the Organization Service WSDL reports a User Principal Name (UPN) instead of an SPN, then the CRM service is configured to run under a domain account. In this case, you must ensure that the domain admin has created an SPN under this service account in AD for the CRM hostname. In this case, the SPN is in the form http://crm.mycompany.com – note that the SPN is typically created to match a fully qualified DNS name that is used to access the CRM service.
Realm: The Domain that the user belongs to. Note that this value is case-sensitive and must be specified exactly as defined in Active Directory.
KDC: This is usually the Domain Controller (server name or IP).

If the environment is complex and requires further settings, manually create a Kerberos configuration file and reference the file in the connector’s connection configuration.

Sample Kerberos configuration file:

[libdefaults]
default_realm = MYREALM.COM
[realms]
MYREALM.COM = {
    kdc = mydomaincontroller.myrealm.com
    default_domain = MYREALM.COM
}
[domain_realm]
.myrealm.com = MYREALM.COM
myrealm.com = MYREALM.COM

Note: The default_realm and default_domain values are case-sensitive. Specify these values exactly as defined in Active Directory. If you receive an error during Test Connection stating Message stream modified (41), the domain name is not correctly formed.

More information on how to create the Kerberos configuration file can be found at http://web.mit.edu/kerberos/krb5-devel/doc/admin/conf_files/krb5_conf.html.

To reference the Kerberos configuration file in a connector’s connection configuration:

Set the property Kerberos Properties File Path
Place the file in the class path (usually under src/main/resources) and set the value of the property to classpath:krb5.conf
Or:
Provide the full path to the file as in C:\kerberos\krb5.conf

You can tune the Kerberos login module (Krb5LoginModule) with scenario-specific configurations by defining a JAAS login configuration file.

Example JAAS login configuration file for the Kerberos login module:

Kerberos {
    com.sun.security.auth.module.Krb5LoginModule required
    debug=true
    refreshKrb5Config=true;
};

For more information on how to create the JAAS login configuration file for the Kerberos login module, see Class Krb5LoginModule.

To reference the JAAS login configuration file for the Kerberos login module in a connector’s connection configuration:

Set the property Login Properties File Path
Place the file in the class path (usually under src/main/resources) and set the value of the property to classpath:jaas.conf

Or:

Provide the full path to the file as in C:\kerberos\jaas.conf

NTLM Authentication

For connecting to Microsoft Dynamics CRM with NTLM authentication, the connector routes requests through Anypoint Platform Gateway Service.

The Anypoint Platform Gateway Service runs as a Windows service. Install using the instructions in the Windows Gateway Service guide on a machine that is joined to the same domain as the Dynamics CRM instance that you want to authenticate against.

Windows Gateway Services has an issue that when installed in the same machine as CRM Dynamics, the Host name is resolved to IPv6, which is not supported by NTLM. So this needs to be accessed through IP. In addition, for CRM Dynamics Connector and Windows Gateway Services, when using the CRM Dynamics Connector using NTLM, HTTPS is not supported.

To install Windows Gateway Service:

Unzip the downloaded file and run the .exe contained within.

For your protection, the executable is signed by MuleSoft Inc.
Follow the instructions to complete the installation. No further configuration is required.

After installing Anypoint Platform Gateway Service, configure the connector’s connection properties with the Username, Password, and the Organization Service URL.

Under NTLM authentication settings, set the Gateway Router Service Address to the address of the Anypoint Platform Gateway Service. This address by default is https://myserver:9333/router.

At this point, the connection should be successfully tested.

CRM Online Authentication

Microsoft Dynamics CRM Online, with Office365, allows federated authentication to known domains. Office365 provides an endpoint to discover the user parameters for federated authentication. In some cases, this discovery is not possible.

For these cases, there are optional connection configuration parameters:

Sts Metadata Url (optional): The STS’s metadata exchange URL. For ADFS, this is usually https://mycompany-sts.com/adfs/services/trust/mex.
Sts Username Port Qname (optional): The name of port that accepts username and password credentials as described in the STS’s metadata exchange URL. Specify this value as a Qname in the format {namespace}/port_name. For ADFS, this is usually:
```
{+http://schemas.microsoft.com/ws/2008/06/identity/securitytokenservice+}UserNameWSTrustBinding_IWSTrust13Async}
```

Proxy

Configure the proxy that is used by the connector. This can be specified in the connector’s Global Element configuration, under the Proxy tab. The value of the proxy address has to be in the format {hostname/IP}:{port}. For example, if the proxy is running in the same server under the port 8080: 127.0.0.1:8080 or localhost:8080.

Metadata caching

The connector does cache metadata by default.

Metadata is retrieved for data sense and also for allow completing some operations. Default configuration is the recommended way to use the connector, but there might be scenarios where often changes on metadata requires not to use this caching feature.

The metadata retrievers are grouped within three categories as described below:

Data sense: As data sense requires all entities to be retrieved, the entities retriever does that and caches it by entity to be reused between different calls. In addition, data sense also exposes attributes for each entity, and this is done by an attributes retriever. For data sense the attributes retriever that is used gets all entities' attributes and caches it (for each one of the entities for which you perform a data sense operation).
Attributes: Some operations within the connector require just to retrieve referenced (by the operation) attributes from a entity. The default attribute retriever for these operations works optimizing data throughput doing single attribute querying, while also doing caching. You can configure these operations (Create, Update, CreateMultiple, UpdateMultiple) behavior to share the data sense retriever if works better on your scenario (ie. if you often create/update entities using most of its attributes).
Relationships: This particular retriever that gets relationships information, and caches it, is just used for the following operations: Associate and Disassociate.

In the table shown below you can find custom configuration settings to disable metadata caching on particular subsets of operations and/or to customize the retrievers behavior on particular cases.

Setting	Usage	Values
org.mule.module.dynamicscrm.metadata.retrievers.nocache	Disable caching for all metadata retrievers	1- disabled, otherwise enabled
org.mule.module.dynamicscrm.metadata.retrievers.entities.nocache	Disable caching for entities metadata retriever used with data sense only	1- disabled, otherwise enabled
org.mule.module.dynamicscrm.metadata.retrievers.relationships.nocache	Disable caching for relationships metadata retriever	1- disabled, otherwise enabled
org.mule.module.dynamicscrm.metadata.retrievers.attributes.nocache	Disable caching for attributes metadata retriever	1- disabled, otherwise enabled
org.mule.module.dynamicscrm.metadata.retrievers.attributes.share	Share attributes metadata retriever (for metadata scopes and connector’s operations). Set this value to '1' to use the full attribute metadata retriever for operations as well as metadata scopes	1- shared, otherwise use single attribute retriever for operations

Setting

Usage

Values

org.mule.module.dynamicscrm.metadata.retrievers.nocache

Disable caching for all metadata retrievers

1- disabled, otherwise enabled

org.mule.module.dynamicscrm.metadata.retrievers.entities.nocache

Disable caching for entities metadata retriever used with data sense only

1- disabled, otherwise enabled

org.mule.module.dynamicscrm.metadata.retrievers.relationships.nocache

Disable caching for relationships metadata retriever

1- disabled, otherwise enabled

org.mule.module.dynamicscrm.metadata.retrievers.attributes.nocache

Disable caching for attributes metadata retriever

1- disabled, otherwise enabled

org.mule.module.dynamicscrm.metadata.retrievers.attributes.share

Share attributes metadata retriever (for metadata scopes and connector’s operations). Set this value to '1' to use the full attribute metadata retriever for operations as well as metadata scopes

1- shared, otherwise use single attribute retriever for operations

These system settings can be passed to the VM executing the mule app by doing:

-Dorg.mule.module.dynamicscrm.metadata.retrievers.nocache=1

Operations

For the technical reference documentation for all connector operations, see the Dynamics CRM APIdoc.

Create Record

Creates a record for an entity.

The following table lists operation inputs:

Property Usage

Property	Usage
Logical Name	The logical name of the entity that the record belongs to.
Attributes	A `Map<String, Object>` with the entity attribute names as the map’s keys. To create a payload for this operation, place a ‘DataWeave’ transformer before the connector in the Mule flow.

Logical Name

The logical name of the entity that the record belongs to.

Attributes

A Map<String, Object> with the entity attribute names as the map’s keys. To create a payload for this operation, place a ‘DataWeave’ transformer before the connector in the Mule flow.

Output: A String containing the ID of the created record.

Create Multiple Records

Creates a set of multiple records for an entity. The following table details the operation inputs.

Property Usage

Property	Usage
Logical Name	The logical name of the entity that the record will belong to.
Attributes List	A `List<Map<String, Object>>` with a list of the entity attribute names as the map’s keys. The payload for this operation can be created easily by placing a ‘DataWeave’ transformer before the connector in the Mule flow.
Use Single Transaction	(Optional) Indicates if Dynamics CRM should use a single transaction to create all items (supported since Microsoft Dynamics CRM 2016).

Logical Name

The logical name of the entity that the record will belong to.

Attributes List

A List<Map<String, Object>> with a list of the entity attribute names as the map’s keys. The payload for this operation can be created easily by placing a ‘DataWeave’ transformer before the connector in the Mule flow.

Use Single Transaction

(Optional) Indicates if Dynamics CRM should use a single transaction to create all items (supported since Microsoft Dynamics CRM 2016).

Output: BulkOperationResult<Map<String,Object>> object

See Data Considerations.

Retrieve Record

Retrieves a single record from an entity.

The following table details the operation inputs.

Property Usage

Property	Usage
Logical Name	The logical name of the entity that the record belongs to.
ID	The ID of the record to update.
Attributes	A `List<String>` with the entity attribute names that returns for the record.

Logical Name

The logical name of the entity that the record belongs to.

The ID of the record to update.

Attributes

A List<String> with the entity attribute names that returns for the record.

Output: Map<String, Object>

The map’s keys are the entity attribute names for the retrieved record.

Retrieve Multiple Records by Query

Retrieves a list of records. This operation leverages Mule’s DSQL for creating the query.

The following table details the operation inputs.

Property	Usage
Query	DataSense Query Language: The DSQL to run. The query is translated by the connector to a Fetch XML. For more information, see DataSense Query Language. Native Query Language: The raw FetchXML to run. More information on how to create this queries can be found at http://msdn.microsoft.com/en-us/library/gg328332.aspx.

Property

Usage

Query

DataSense Query Language: The DSQL to run. The query is translated by the connector to a Fetch XML. For more information, see DataSense Query Language.

Native Query Language: The raw FetchXML to run. More information on how to create this queries can be found at http://msdn.microsoft.com/en-us/library/gg328332.aspx.

Output: ProviderAwarePagingDelegate<Map<String, Object>, DynamicsCRMConnector>

In a Mule flow, this passes on to the next flow component a List<Map<String, Object>, where each Map<String, Object> element in the list contains a record of the queried entity. The map’s keys are the entity attribute names for the records.

Update Record

Updates an existing record in an entity.

The following table lists operation inputs:

Property Usage

Property	Usage
Logical Name	The logical name of the entity that the record belongs to.
ID	The ID of the record to update.
Attributes	A `Map<String, Object>` with the entity attribute names as the map’s keys. To create a payload for this operation, place a ‘DataWeave’ transformer before the connector in the Mule flow.

Logical Name

The logical name of the entity that the record belongs to.

The ID of the record to update.

Attributes

A Map<String, Object> with the entity attribute names as the map’s keys. To create a payload for this operation, place a ‘DataWeave’ transformer before the connector in the Mule flow.

Output: Void. This operation does not return a value.

Update Multiple Records

Updates several existing records in an entity.

The following table details the operation inputs.

Property Usage

Property	Usage
Logical Name	The logical name of the entity that the record belongs to.
Attributes List	A `List<Map<String, Object>>` with the entity attribute names as the map’s keys. The payload for this operation can be created easily by placing a ‘DataWeave’ transformer before the connector in the Mule flow.
Use Single Transaction	(Optional) Indicates if Dynamics CRM should use a single transaction to update all items (supported since Microsoft Dynamics CRM 2016).

Logical Name

The logical name of the entity that the record belongs to.

Attributes List

A List<Map<String, Object>> with the entity attribute names as the map’s keys. The payload for this operation can be created easily by placing a ‘DataWeave’ transformer before the connector in the Mule flow.

Use Single Transaction

(Optional) Indicates if Dynamics CRM should use a single transaction to update all items (supported since Microsoft Dynamics CRM 2016).

Output: BulkOperationResult<Map<String,Object>> object

Delete Record

Deletes a record from an entity.

The following table lists operation inputs:

Property	Usage
Logical Name	The logical name of the entity that the record belongs to.
ID	The ID of the record to delete.

Property

Usage

Logical Name

The logical name of the entity that the record belongs to.

The ID of the record to delete.

Output: Void. This operation does not return a value.

Delete Multiple Records

Deletes multiple records from an entity.

The following table details the operation inputs.

Property Usage

Property	Usage
Logical Name	The logical name of the entity that the record belongs to.
Ids	The `List<String>` with the ids of the records to delete.
Use Single Transaction	(Optional) Indicates if Dynamics CRM should use a single transaction to delete all items (supported since Microsoft Dynamics CRM 2016).

Logical Name

The logical name of the entity that the record belongs to.

Ids

The List<String> with the ids of the records to delete.

Use Single Transaction

(Optional) Indicates if Dynamics CRM should use a single transaction to delete all items (supported since Microsoft Dynamics CRM 2016).

Output: BulkOperationResult<String> object

Associate Records

Creates a link between records.

The following table details the operation inputs:

Property Usage

Property	Usage
Logical Name	The logical name of the entity that the record belongs to.
ID	The ID of the record to which the related records are associated.
Schema Name	The name of the relationship to create the link.
Entity Role Is Referenced	When associating records from the same entity (reflexive relationship), set this property as follows: `false`: When the primary entity record References the record to associate. `true`: When the primary entity record is Referenced by the record to associate.
Related Entities	A `List<Map<String, Object>>` with the related entity records to associate. Each `Map<String, Object>` contains two keys: `logicalName`: The logical name of the entity that the record to associate belongs to. `id`: The ID of the record to associate.

Logical Name

The logical name of the entity that the record belongs to.

The ID of the record to which the related records are associated.

Schema Name

The name of the relationship to create the link.

Entity Role Is Referenced

When associating records from the same entity (reflexive relationship), set this property as follows:

false: When the primary entity record References the record to associate.
true: When the primary entity record is Referenced by the record to associate.

Related Entities

A List<Map<String, Object>> with the related entity records to associate.

Each Map<String, Object> contains two keys:

logicalName: The logical name of the entity that the record to associate belongs to.
id: The ID of the record to associate.

Output: Void. This operation does not return a value.

Disassociate Records

Deletes a link between records.

The following table details the operation inputs.

Property Usage

Property	Usage
Logical Name	The logical name of the entity that the record belongs to.
ID	The ID of the record from which the related records are disassociated.
Schema Name	The name of the relationship to delete the link.
Entity Role Is Referenced	When disassociating records from the same entity (reflexive relationship), set this property as follows: `false`: When the primary entity record References the record to associate. `true`: When the primary entity record is Referenced by the record to associate.
Related Entities	A `List<Map<String, Object>>` with the related entity records to disassociate. Each `Map<String, Object>` contains two keys: `logicalName`: The logical name of the entity that the record to disassociate belongs to. `id`: The ID of the record to disassociate.

Logical Name

The logical name of the entity that the record belongs to.

The ID of the record from which the related records are disassociated.

Schema Name

The name of the relationship to delete the link.

Entity Role Is Referenced

When disassociating records from the same entity (reflexive relationship), set this property as follows:

false: When the primary entity record References the record to associate.
true: When the primary entity record is Referenced by the record to associate.

Related Entities

A List<Map<String, Object>> with the related entity records to disassociate.

Each Map<String, Object> contains two keys:

logicalName: The logical name of the entity that the record to disassociate belongs to.
id: The ID of the record to disassociate.

Output: Void. This operation does not return a value.

Execute

Executes a Dynamics CRM organization request and returns the response. The following table details the operation inputs.

Property	Usage
Request Name	The request name to execute.
Request Id	(Optional) The ID of the request.
Request Parameters	The request parameters are taken from the message Payload. To set these parameters correctly for each operation, a ‘DataWeave’ is typically used before the connector is called. In addition of using a POJO (from the OrganizationRequest hierarchy tree), this operation supports providing the payload as a Map<String, Object> (which is the most efficient/compact way of usage).

Property

Usage

Request Name

The request name to execute.

Request Id

(Optional) The ID of the request.

Request Parameters

The request parameters are taken from the message Payload. To set these parameters correctly for each operation, a ‘DataWeave’ is typically used before the connector is called.

In addition of using a POJO (from the OrganizationRequest hierarchy tree), this operation supports providing the payload as a Map<String, Object> (which is the most efficient/compact way of usage).

Output: A POJO (from the OrganizationResponse hierarchy tree) containing the results of the method executed. The structure of each response is described in the operation’s metadata.

Supported Operations: The full set of the Microsoft Dynamics CRM organization request entities described at Microsoft.Crm.Sdk.Messages and Microsoft.Xrm.Sdk.Messages namespaces (operation availability depends on the Microsoft Dynamics CRM version you are working with - check the documentation related to yours).

Execute Multiple

Executes multiple Dynamics CRM organization requests and returns their responses. The following table details the operation inputs.

Property	Usage
Requests	The requests are taken from the message Payload. To set these parameters correctly for each operation, a ‘DataWeave’ is typically used before the connector is called. In addition of using an array or list with POJOs (from the OrganizationRequest hierarchy tree), this operation supports providing the payload as a list or array of Map<String, Object> (which is the most efficient/compact way of usage).
Request Id	(Optional) The ID of the request.
Use Single Transaction	(Optional) Indicates if Dynamics CRM should use a single transaction to execute all items (supported since Microsoft Dynamics CRM 2016).

Property

Usage

Requests

The requests are taken from the message Payload. To set these parameters correctly for each operation, a ‘DataWeave’ is typically used before the connector is called.

In addition of using an array or list with POJOs (from the OrganizationRequest hierarchy tree), this operation supports providing the payload as a list or array of Map<String, Object> (which is the most efficient/compact way of usage).

Request Id

(Optional) The ID of the request.

Use Single Transaction

(Optional) Indicates if Dynamics CRM should use a single transaction to execute all items (supported since Microsoft Dynamics CRM 2016).

Output: BulkOperationResult<OrganizationResponse> object (from the OrganizationResponse hierarchy tree) containing the results of the requests executed.

Exceptions Handling

Exceptions when Connecting

If the connector fails to connect with the CRM instance for any reason, an exception of type ConnectionException is thrown. The exception message helps debugging the cause of the exception.

Exceptions in Operations

Each operation throws a different type of exception. This is useful when defining an exception handling policy.

The following table lists the exception types that are thrown for every operation.

Operation	Exception Type
Create	IOrganizationServiceCreateOrganizationServiceFaultFaultFaultMessage
Create Multiple	IOrganizationServiceExecuteOrganizationServiceFaultFaultFaultMessage
Update	IOrganizationServiceUpdateOrganizationServiceFaultFaultFaultMessage
Update Multiple	IOrganizationServiceExecuteOrganizationServiceFaultFaultFaultMessage
Delete	IOrganizationServiceDeleteOrganizationServiceFaultFaultFaultMessage
Delete Multiple	IOrganizationServiceExecuteOrganizationServiceFaultFaultFaultMessage
Retrieve	IOrganizationServiceRetrieveOrganizationServiceFaultFaultFaultMessage
Retrieve Multiple	IOrganizationServiceRetrieveMultipleOrganizationServiceFaultFaultFaultMessage
Associate	IOrganizationServiceAssociateOrganizationServiceFaultFaultFaultMessage
Disassociate	IOrganizationServiceDisassociateOrganizationServiceFaultFaultFaultMessage
Execute	IOrganizationServiceExecuteOrganizationServiceFaultFaultFaultMessage
Execute Multiple	IOrganizationServiceExecuteOrganizationServiceFaultFaultFaultMessage

Operation

Exception Type

Create

IOrganizationServiceCreateOrganizationServiceFaultFaultFaultMessage

Create Multiple

IOrganizationServiceExecuteOrganizationServiceFaultFaultFaultMessage

Update

IOrganizationServiceUpdateOrganizationServiceFaultFaultFaultMessage

Update Multiple

IOrganizationServiceExecuteOrganizationServiceFaultFaultFaultMessage

Delete

IOrganizationServiceDeleteOrganizationServiceFaultFaultFaultMessage

Delete Multiple

IOrganizationServiceExecuteOrganizationServiceFaultFaultFaultMessage

Retrieve

IOrganizationServiceRetrieveOrganizationServiceFaultFaultFaultMessage

Retrieve Multiple

IOrganizationServiceRetrieveMultipleOrganizationServiceFaultFaultFaultMessage

Associate

IOrganizationServiceAssociateOrganizationServiceFaultFaultFaultMessage

Disassociate

IOrganizationServiceDisassociateOrganizationServiceFaultFaultFaultMessage

Execute

IOrganizationServiceExecuteOrganizationServiceFaultFaultFaultMessage

Execute Multiple

IOrganizationServiceExecuteOrganizationServiceFaultFaultFaultMessage

Maven Dependency Snippet

Make sure that this snippet is included in your Maven project using the connector.

<dependency>
            <groupId>org.mule.modules</groupId>
            <artifactId>mule-module-ms-dynamics-crm</artifactId>
            <version>2.8.0</version>
        </dependency>

Data Considerations

Entity Reference

Entity reference attributes are accessible as String values that match the pattern myattribute_referenceto_targetentity.

To avoid conflicts, don’t add fields to your CRM instance using this reserved naming scheme: referenceto[].

As an example, the Contact Entity Reference attribute TransactionCurrencyId is Lookup field that targets the entity transactioncurrency. The transactioncurrencyid of the transactioncurrency is accessible as a String in the attribute transactioncurrencyid_referenceto_transactioncurrency.

The Create and Update operations accept entity reference attributes. Following the example above, to create a Contact targeting a transactioncurrency, set the value of the attribute transactioncurrencyid_referenceto_transactioncurrency to the transactioncurrencyid of the record to reference.

The Retrieve Multiple Records operation also allows selecting and filtering of Entity Reference attributes. As an example for Contact, the following DataSense Query returns all the contact full names that where created by a particular systemuserid:

Select fullname From contact Where createdby_referenceto_systemuser =
'c7a58b13-df19-491c-a918-1bc26eaf6eb3'

Party List

A Party List is typically found on email activities to represent the To, Bcc, and Cc attributes. This type of attribute is accessible as a list of Map<String, String> objects where each list item represents an Entity Reference.
As an example, the Email Party List attribute To is a list of Lookup objects that can target any of the following entities: Account, Contact, Lead, Queue, and SystemUser.

The To attribute is a List of Map<String, String> objects where each Map’s key is one of the following:

to_referenceto_account, to_referenceto_contact, to_referenceto_lead, to_referenceto_queue or to_referenceto_systemuser

For an email sent to an account and a contact, the To attribute is:

[{ to_referenceto_account: 40f5b94e-1cb6-45c1-9990-76fb7f038447}, { to_referenceto_contact: 3b7d2441-6fc7-48be-a965-a89e501ad5b3} ]

Picklist

Picklist attributes are accessible as Integer values.

As an example, the Contact attribute familystatuscode is accessible as an Integer value.

Money

Money attributes are accessible as BigDecimal values.

As an example, the Contact attribute creditlimit is accessible as a BigDecimal value.

BulkOperationResult<T>

isSuccessful() returns a Boolean value. Is false if any of the results contains an error.
getItems() returns a list of the results. Each result has a correlation and respects the order of the record Created, Updated, or Deleted.
Each item has the following data:
- isSuccessful() is false if the operation is faulted.
- getId() returns the ID of the created entity in create-multiple operation.
- getException() returns the Exception from the backend fault.
- getMessage() returns the message in case isSuccessful() is false.

Frequently Asked Questions

Which versions of Dynamics CRM are supported by this connector?

See Supported versions in the Overview section for the current list of supported CRM versions.

What authentication schemes are supported by the connector?

Options for authentication against on-premises CRM instances include Kerberos, Claims Authentication (ADFS), and NTLM (via the Anypoint platform gateway for Windows). For CRM Online, the standard CRM online authentication protocol is supported.

What parts of the CRM object model are accessible by the connector?

All out-of-box and custom entities are available via the connector, including primary entities and association entities.

Are DataSense and DataWeave supported by this connector?

Yes, all entities and entity attributes are exposed to Studio by the connector for use with DataWeave and DataSense.

What operations can I perform with the connector?

All standard create-read-update-delete operations are supported against all CRM entities. Additionally, queries for collections of objects can be written either in native FetchXML or Mule’s DSQL query language.

Are there any examples that show how to use the connector?

Yes, an example project for Anypoint Studio is available in dynamics-crm-connector-samples.zip.

What Mule editions can I use this connector on?

This connector is supported on any Enterprise Edition Anypoint platform running on any operating system and bit-ness, including the CloudHub integration PaaS.

Microsoft Dynamics CRM Connector

Overview

Installing and Configuring

Configuring the Connector

Step 1: Create a New Mule Project

Step 2: Configure the Global Element

Creating a Mule Flow

Running a Flow

CRM Authentication

Authentication Schemes

Advanced Kerberos Authentication

NTLM Authentication

CRM Online Authentication

Proxy

Metadata caching

Operations

Create Record

Create Multiple Records

Retrieve Record

Retrieve Multiple Records by Query

Update Record

Update Multiple Records

Delete Record

Delete Multiple Records

Associate Records

Disassociate Records

Execute

Execute Multiple

Exceptions Handling

Exceptions when Connecting

Exceptions in Operations

Maven Dependency Snippet

Data Considerations

Entity Reference

Party List

Picklist

Money

BulkOperationResult<T>

Frequently Asked Questions

Which versions of Dynamics CRM are supported by this connector?

What authentication schemes are supported by the connector?

What parts of the CRM object model are accessible by the connector?

Are DataSense and DataWeave supported by this connector?

What operations can I perform with the connector?

Are there any examples that show how to use the connector?

What Mule editions can I use this connector on?

See Also