DEPRECATED | Dynamics CRM Update
On this Page
This property enables you to execute the Snap during the Save operation so that the output view can produce the preview data.
| Snap type: | Write | ||||||
|---|---|---|---|---|---|---|---|
| Description: | This Snap provides functionality to update an existing record in Microsoft Dynamics CRM. ETL Transformations & Data Flow This Snap enables the following ETL operations/flows:
Input & Output
| ||||||
| Prerequisites: | [None] | ||||||
| Limitations and Known Issues: |
| ||||||
| Configurations: | Account and Access This Snap uses account references created on the Accounts page of SnapLogic Manager to handle access to this endpoint. See Dynamics CRM Account for information on setting up this type of account. Views
| ||||||
| Troubleshooting: | For trouble shooting purpose, try performing a similar operation directly on the Dynamics CRM User Interface and collect the necessary data. Compare the data used in the User Interface with the SnapLogic pipelines to see if there are any inconsistencies. In order to view the Object ID of the Dynamics CRM Object from the User Interface, the recommended approach is to install a browser plug-in. The plug-in will be available in the browser's Developer tools console. Contact your administrator for the preferred plug-in. | ||||||
Settings | |||||||
Label | Required. The name for the Snap. You can modify this to be more specific, especially if you have more than one of the same Snap in your pipeline. | ||||||
Object type | Required. Microsoft Dynamics CRM Object Type. Example: account. Default Value: account Imp. for adding activity type entity When configuring activity type entities, such as Task, PhoneCall, Fax, etc., if the parameter regardingobjectid is also being added then map a logical name as well, this can be done by adding the parameter regardingobjectname. If this is not done, the Snap will throw an exception. | ||||||
| ID | Required. Guid of the Dynamics CRM Object. This field is suggestible. | ||||||
| Related object type | Microsoft Dynamics CRM Object Type of the Object to be related to. Default Value: None | ||||||
| Related object relationship | Relationship Schema between the Microsoft Dynamics Object to be created with the related Object. Default Value: None | ||||||
| Related object ID | Guid of the related Microsoft Dynamics CRM Object. Default Value: None | ||||||
| Batch Size | Required. Number of records processed in each request. Batch size range is from 1 to 1000. Default Value: 200 | ||||||
Snap execution | Select one of the three modes in which the Snap executes. Available options are:
| ||||||
Basic Use Case
The following pipeline describes how the Snap functions as a standalone Snap in a pipeline with an ID provided manually:
.png?version=1&modificationDate=1492585581054&cacheVersion=1&api=v2)
Typical Snap Configuration
The Key Snap configurations are:
- Without Expressions
In this pipeline, the Dynamics CRM Update Snap updates the Object type, contact by providing the ID manually:
- With Expressions
- Query from Upstream
In this pipeline, the Dynamics CRM Update Snap updates the CRM Object with the ID as provided by the upstream CSV Generator Snap and the field to be updated via the Mapper Snap.
The IDs as passed by the CSV Generator Snap:
The Mapper Snap provides the field to be updated with the value:
The Dynamics CRM Snap updates the Object type Contact, with the provided ID as taken from the upstream:
The successful execution of the pipeline displays the below output:
- Pipeline Parameter
In this pipeline, the pipeline parameters are as set to be passed to the CRM Update Snap:
Advanced Use Case
The following describes a pipeline, with a broader business logic involving multiple ETL transformations, that shows how typically in an enterprise environment, CRM Update functionality is used. The pipeline download is available below.
This pipeline reads and moves files from the ServiceNow instance to the Dynamics CRM instance.
- Extract: The ServiceNow Query Snap extracts the documnets from the ServiceNow instance.
- Transform: The Mapper Snap maps the input schema to the target fields on the ServiceNow instance.
- Transform: The Head Snap retrieves the needed documents (here the first five) in order from the top.
- Transform: The second Mapper Snap maps the documents to passed to the CRM instance.
- Transform: The third Mapper Snap maps the input schema to the target fields that are to be updated.
- Load: The CRM Create Snap cretaes the entity on the CRM instance.
- Load: The ServiceNow Snap updates the documensts as retrieved from the ServiceNow Query.
- Load: The Dynamics CRM Update Snap updates the object type.
Downloads
Important steps to successfully reuse Pipelines
- Download and import the Pipeline into SnapLogic.
- Configure Snap accounts as applicable.
- Provide Pipeline parameters as applicable.
Snap Pack History
Have feedback? Email documentation@snaplogic.com | Ask a question in the SnapLogic Community
© 2017-2024 SnapLogic, Inc.