Skip to end of banner
Go to start of banner

WIP - Dynamics 365 Finance and SCM Update

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 26 Next »

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 seconds

    Refer 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

  • 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 ((blue star)): Indicates a list that is dynamically populated based on the configuration.

  • Expression icon ((blue star) ): Indicates the value is an expression (if enabled) or a static value (if disabled). Learn more about Using Expressions in SnapLogic.

  • Add icon ( (blue star) ): Indicates that you can add fields in the field set.

  • Remove icon ( (blue star)): Indicates that you can remove fields from the field set.

  • Upload icon ((blue star) ): Indicates that you can upload files.

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.

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.

The number of retries are disabled if the value is 0.

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

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 For Sales endpoint.

The Microsoft Dynamics 365 For Sales 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.

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

  File Modified
No files shared here yet.

Snap Pack History

 Click here to expand...

Release

Snap Pack Version

Date

Type

Updates

November 2024

main29029

Stable

Updated and certified against the current Snaplogic Platform release.

August 2024

main27765

Stable

Updated and certified against the current SnapLogic Platform release.

May 2024

main26341

Stable

Updated and certified against the current SnapLogic Platform release.

February 2024

436patches26143

Latest

Fixed an issue with the Dynamics 365 Finance and SCM Bulk Export Snap that displayed the error message twice when:

  • Operation is Trigger Export

  • Definition group ID is incorrect

  • When error occurs  is Stop Pipeline Execution (Views tab)

February 2024

436patches25295

Latest

Fixed an issue with the recurring bulk import operation for the Recurring Integrations API integration type in the Dynamics 365 Finance and SCM Bulk Import Snap, which previously displayed an error at the preprocessing step intermittently.

February 2024

main25112

Stable

Updated and certified against the current SnapLogic Platform release.

November 2023

435patches24298

Latest

Added the following Snaps in the Microsoft Dynamics 365 Finance and SCM Snap Pack:

November 2023

main23721

Stable

Updated and certified against the current SnapLogic Platform release.

August 2023

434patches23466

Latest

Enhanced the Dynamics 365 Finance and SCM Read and Dynamics 365 Finance and SCM Search Snaps with the Error out on no results checkbox, which customizes the error view when no results are returned.

August 2023

434patches23129

Latest

  • The Cross company checkbox is added to the Dynamics 365 Finance and SCM CreateUpdate, and Delete Snaps to ensure that the other company records are getting created, updated, and deleted.

  • Fixed an issue with the Microsoft Dynamics Finance and SCM Snaps that failed when the string values (filter criteria) are passed without quotes.

  • Fixed an issue with the Microsoft Dynamics Finance and SCM Snap that failed to execute after processing less number of records.

August 2023

434patches22601

Latest

August 2023

main22460

Stable

Updated and certified against the current SnapLogic Platform rThe Cross company checkbox is added to the Dynamics 365 Finance and SCM CreateUpdate, and Delete Snaps to ensure that the other company records are getting created, updated, and deleted.

May 2023

main21015

Stable

Upgraded with the latest SnapLogic platform release.

February 2023

432patches20657

Latest

Added the Dynamics 365 Finance and SCM Create, Update, and Delete Snaps to the Microsoft Dynamics 365 Finance and Supply Chain Management Snap Pack.

February 2023

432patches20035

Latest

Introduced the Microsoft Dynamics 365 Finance and SCM Snap Pack. This Snap Pack contains the following Snaps and accounts:


Related Content

  • No labels