In this article

Overview

This Snap enables you to update an existing record or insert a new record in MS Dynamics 365 for Sales based on the input document field values that match the MS Dynamics 365 for Sales object schema field names.

Input & Output

• Expected upstream Snaps: Any Snap, such as the Mapper Snap, that offers a document view as output.
• Expected downstream Snaps: None

• Input: Fields of the MS Dynamics 365 for Sales object to be updated or created. It is optional to provide either the ID of the object or to use a query. If an ID or query is provided, then the corresponding record is updated; else new record(s) are created. The typical configuration is to have an upstream Snap that contains the mandatory fields for updating the existing MS Dynamics 365 for Sales object. Mapper Snap is a preferred upstream Snap as it populates the input schema for the selected MS Dynamics 365 for Sales object type.

• Output: A document with the result set. If the update is successful, then the output document contains the GUID of the updated or inserted MS Dynamics 365 for Sales object.

You must have a Dynamics 365 OAuth2 for an Online account, data to query, and access to the objects concerned.

Configuring Accounts

This Snap uses account references created on the Accounts page of SnapLogic Manager to handle access to this endpoint. See Configuring Dynamics 365 for Sales Accounts for information on setting up this type of account.

Configuring Views

Troubleshooting

For troubleshooting purposes, try performing a similar operation directly on the MS Dynamics 365 for Sales console and collect the necessary data. Compare the data used in the user interface with the SnapLogic pipelines to see if there are any inconsistencies.

Limitations and Known Issues

• When deleting more than one object in batches, the Batch Size range is from 1 to 1000. This is a limitation by Microsoft Dynamics 365 for Sales.
• MS Dynamics 365 for Sales limits the number of API calls to 60,000 per minute, per user org.  This should be considered when configuring the size of any batch process.
• The Object Type suggestions are limited to the object types available within MS Dynamics 365 for Sales v8.2 and v9.0. There is no current ability to suggest custom object types.

• This Snap cannot create relationships using collection-valued navigation properties, such as contact_customer_accounts, due to current WebAPI limitations; however, it works correctly with single-valued navigation properties, such as primarycontactid.

Modes

• Ultra Pipelines: Works in Ultra Pipelines.
  
  

Snap Settings

Examples

Updating customer details using Dynamics 365 for Sales Upsert Snap

Following is a detailed example that uses Upsert Query. The following Pipeline uses Snaps like Dynamics 365 for Sales Create, Dynamics 365 for Sales Read and Dynamics 365 for Sales Delete Snaps to create customer details from the sales report, read them, upsert them, whenever required, and delete them if required. 

First, in this Pipeline, using the Mapper Snap, the details of the customer like Account ID, Batch size, and Page number are given as inputs.

Create these details from the Mapper Snap with the help of Dynamics 365 for Sales Create Snap.

Next, another Mapper Snap to add more details to the list of customer details:

Update these details using Dynamics 365 for Sales for Upsert Snap. 

These results are copied and routed into two outputs. One output is to get these details and save them for further use and another output is used to delete the details using Dynamics 365 for Sales Delete Snap. 

Updating the Attributes of an Object

Basic use case, using the Dynamics 365 for Sales Upsert Snap with a Mapper

Downloads

Related Links

• Organization Service Create Method
• Organization Service Update Method