Versions Compared

Old Version 5

changes.mady.by.user Lakshmi Manda

Saved on

compared with

New Version Current

changes.mady.by.user Gouri Bhagchandani

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Table of Contents
minLevel1
maxLevel6
outlinefalse
typelist
printablefalse

Overview

You can use the Dynamics 365 Business Central Update Snap to update the user records for an entity.

The Business Central Create Update Snap does not allow upstream values for any fields (Company, Entity, etc.).

...

Snap Type

The Dynamics 365 Business Central Update Snap is a Write-type Snap.

Prerequisites

A valid Business Central Access Token Account or OAuth2 Account with the required permissions.

Support for Ultra Pipelines

Works in Ultra Pipelines. 

Limitations

  • The Business Central Update Snap supports a maximum Batch size of 100.

  • The Business Central Create, Update, and Delete Snaps do not support the respective operations for a few entities, such as Account, and display an exception when you perform createcreating, updateupdating, or delete deleting operations. Learn more about the API limitations: API documentation for Business Central.

Known Issues

  • The Company field in the Business Central Update is optional for a few entities, such as Subscriptions, whereas and it is mandatory for the remaining entities. Therefore, if the field is left blank, the Snap displays the following error:

    Workaround: Specify the Company name for entities where it is mandatorymandatory entities.

  • The Microsoft Dynamics 365 Business Central Update Snap displays the following errors when you 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 decrease the batch size while keeping the default retry properties.

Snap Views

Type

Format

Number of Views

Examples of Upstream and Downstream Snaps

Description

Input 

Document

 

  • Min: 1

  • 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

Info

  • 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 Value: Dynamics 365 Business Central Update
Example: BC 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.

 

Company

Default Value: N/A
Example: My Company

String/Expression/Suggestion

Specify the company registered with the Business Central application.

Entity*

 

Default Value: N/A.
Example:

Employees

employees

String/Expression/Suggestion

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
Example: Id

String/Expression/Suggestion

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 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
Example: 2998d72e-fac9-ed11-94cc-000d3a220b2f

String/Expression

Specify the value of the key for which you want to update the record.

Batch type

Default Value: Stop-On-Error
Example: Transactional

Dropdown list

Choose the operation you want for batching, which is applicable only when the Batch size is more than 1:

  • Stop-On-Error: Sends all the records to the output view until the Snap encounters an error.

  • Transactional: Sends all the records and the records with errors to the error view when an error occurs.

  • Continue-On-Error: Sends all the records except those with the error to the output view.

Batch size

 

Default Value: 100
Example: 50

Integer/Expression

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

Timeout (seconds)

 

Default Value: 60
Example: 100

Integer/Expression

Specify the timeout to determine whether the connection is alive and also specify the timeout

while

when waiting for a response through the socket.

Number of retries

 

Default Value: 0
Example: 5

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
Example: 5

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 Business Central 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.

Decrease the batch size and retry. Learn more about the error messages: Service protection API limits.

Too many Requests - 429.

There are too

Too many requests were sent to the Business Central endpoint.

The Snaps related to Microsoft Business Central

related Snaps

, include retry-after with <number of seconds> in the response header and automatically

retries

retry when they encounter a status 429 error. Therefore, wait for the retry to succeed.

Examples

Refer to this example to understand the function of Business Central Update Snap.

Snap Pack History

info
Expand
titleClick here to expand...

Insert excerpt
Microsoft Dynamics 365 Business Central
Microsoft Dynamics 365 Business Central
nameMicrosoft Dynamics 365 Business Central
nopaneltrue

Related Content

...

...