Dynamics 365 Finance and SCM Update

In this article

Overview

You can use 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 seconds

    Refer to Service protection API limits - Finance & Operations for more information.
    Workaround: 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

The Microsoft Dynamics 365  Finance and SCM Update Snap displays the following errors when we run the batch process with the error view enabled.

  • 500 ( Internal Server Error)

  • Socket timeout error

  • Read timed out error

Workaround: Increase the Timeout value to 500 or more and also decrease the batch size, along with the default retry properties.

Snap Views

Type

Format

Number of Views

Examples of Upstream and Downstream Snaps

Description

Type

Format

Number of Views

Examples of Upstream and Downstream Snaps

Description

Input 

Document

 

  • Min: 0

  • Max: 1

  • Mapper

Requires the data that you need to update.

Output

Document

 

  • Min: 1

  • Max: 1

  • Mapper

  • Union

  • Copy

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:

  • Stop Pipeline Execution: Stops the current pipeline execution if the Snap encounters an error.

  • Discard Error Data and Continue: Ignores the error, discards that record, and continues with the remaining records.

  • Route Error Data to Error View: Routes the error data to an error view without stopping the Snap execution.

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

Field Name

Field Type

Description

Label*

 

Default ValueDynamics 365 Finance and SCM Update
ExampleF&SCM Update

String

Specify a unique 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.

 

Entity*

 

Default Value: N/A.
Example: People

String/Expression

Specify the OData entity object.

Cross company

 

Default ValueDeselected

Checkbox

Select this checkbox to update record (apart from default company) for an entity.

Primary key*

Use this field set to specify the primary key that uniqely identifies the rows.

Key

 

Default Value: N/A
ExamplePartyNumber

String/Expression

Specify or select the primary key from which you want to update the record.

  • More than one primary key can exist for an Entity.

  • Ensure that you provide key-value pairs for the primary keys, which are associated with a specific entity. If you do not specify, the Snap fails. For example, if you have four Primary keys in an entity, then you must pass the value for every field to fetch the results. If you use only one of the primary keys, the Snap fails.

Value

 

Default Value: N/A
Example0000032

String/Expression

Specify the value of the key from which you want to read the record.

Batch size

 

Default Value1
Example: 100

Integer/Expression

Specify the batch size to update the records in the specified batch in the application.

Timeout (seconds)

 

Default Value300
Example: 100

Integer

Specify the timeout to determine whether the connection is alive and also timeout while waiting for response through socket.

Number of retries

 

Default Value0
Example5

Integer/Expression

Specify the maximum number of attempts to be made to receive a response.

Retry interval (seconds)

 

Default Value1
Example5

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
Example
Accept

String/Expression

Specify the key for the HTTP header.

Value

 

Default Value: N/A
Example

application/json;odata.metadata=full

String/Expression

Specify the value for the HTTP header.

Snap Execution

 

Default Value
Example: Validate & Execute

Dropdown list

Select one of the following three modes in which the Snap executes:

  • Validate & Execute: Performs limited execution of the Snap, and generates a data preview during pipeline validation. Subsequently, performs full execution of the Snap (unlimited records) during pipeline runtime.

  • Execute only: Performs full execution of the Snap during pipeline execution without generating preview data.

  • Disabled: Disables the Snap and all Snaps that are downstream from it.

Troubleshooting

Error

Reason

Resolution

Error

Reason

Resolution

Number of requests exceeded the limit of 6000 over the time window of 300 seconds

Requests exceeded the limit of 6000 over the time window of 300 seconds.

You must decrease the batch size and retry.

Too many Requests - 429

There are too many requests sent to Dynamics 365 Finance and SCM endpoint.

The Microsoft Dynamics 365 Finance and SCM related Snaps, include retry-after with <number of seconds> in the response header and automatically retries when they encounter status 429 error. Therefore, wait for the retry to succeed.

Error while executing the request.

No resources were found when performing the update action.

The record might belong to other company, therefore select the Cross company checkbox 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:

Download this pipeline

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.

Downloads