In this article
Overview
You can use the Dynamics 365 Finance and SCM Update Snap to update the user records for an entity.
When you use the Mapper Snap to pass input data to the Dynamics 365 Finance and SCM Update Snap, the input schema populates only the columns that you can update.
You must pass only one record at a time using the Primary key field to update the user data. You can pass upstream values (in the Mapper Snap) if you want to perform bulk operations.
Snap Type
The Dynamics 365 Finance and SCM Update Snap is a Write-type Snap.
Prerequisites
A valid Finance and SCM Access Token Account or OAuth2 Account with the required permissions.
Support for Ultra Pipelines
Works in Ultra Pipelines.
Limitations
Based on your environment configurations, when the Batch size increases, the Snap might fail because of an API limitation and displays the following error message:
Number of requests exceeded the limit of 6000 over the time window of 300 secondsRefer to Service protection API limits - Finance & Operations for more information.
Work-around: You must decrease the batch size and retry.The Snap fails and updates the error view with the error message from API when you pass invalid values for a mandatory field.
Known Issues
None.
Snap Views
Type | Format | Number of Views | Examples of Upstream and Downstream Snaps | Description |
|---|---|---|---|---|
Input | Document |
|
| Requires the data that you need to update. |
Output | Document |
|
| The data is written to the endpoint. |
Error | Error handling is a generic way to handle errors without losing data or failing the Snap execution. You can handle the errors that the Snap might encounter when running the Pipeline by choosing one of the following options from the When errors occur list under the Views tab:
Learn more about Error handling in Pipelines. | |||
Snap Settings
Asterisk ( * ): Indicates a mandatory field.
Suggestion icon (
): Indicates a list that is dynamically populated based on the configuration.Expression icon (
): Indicates the value is an expression (if enabled) or a static value (if disabled). Learn more about Using Expressions in SnapLogic.Add icon (
): Indicates that you can add fields in the field set.Remove icon (
): Indicates that you can remove fields from the field set.Upload icon (
): Indicates that you can upload files.
Field Name | Field Type | Description | |
|---|---|---|---|
Label*
Default Value: Dynamics 365 Finance and SCM Update | String | Specify a unique name for the Snap.
| |
Entity*
Default Value: N/A. | String/Expression | Specify the OData entity object. | |
Primary key* | Use this field set to specify the primary key that uniqely identifies the rows. | ||
Key Default Value: N/A | String/Expression | Specify or select the primary key from which you want to update the record.
| |
Value Default Value: N/A | String/Expression | Specify the value of the key from which you want to read the record. | |
Batch size Default Value: 1 | Integer/Expression | Specify the batch size to update the records in the specified batch in the application. | |
Number of retries Default Value: 0 | Integer/Expression | Specify the maximum number of attempts to be made to receive a response. The number of retries are disabled if the value is 0. | |
Retry interval (seconds) Default Value: 1 | Integer/Expression | Specify the amount of time in seconds between retry attempts | |
HTTP header | Use this field set to define the HTTP key-value pairs to pass to the Dynamics 365 Finance and SCM instance. | ||
Key Default Value: N/A | String/Expression | Specify the key for the HTTP header. | |
Value Default Value: N/A application/json;odata.metadata=full | String/Expression | Specify the value for the HTTP header. | |
Snap Execution Default Value: | Dropdown list | Select one of the following three modes in which the Snap executes:
| |
Troubleshooting
Error | Reason | Resolution |
|---|---|---|
| Requests exceeded the limit of 6000 over the time window of 300 seconds. | You must decrease the batch size and retry. |
Examples
Updating a New Attribute in the Existing Records
This example pipeline demonstrates how to update an existing record in the Finance and Operations endpoint:
Step 1: Configure the Mapper Snap with the attributes you want to update in the existing records.
Step 2: Configure the following fields in the Dynamics 365 Finance and SCM Update Snap:
a. Entity field.
b. Primary key to update the required attribute.
Step 3: Validate the Snap. On validation, the output displays the updated status and attribute.
