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.

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

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.

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 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 timeout while waiting for response through socket.

Number of retries

Default Value: 0
Example: 5

Integer/Expression

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

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.

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 many requests sent to Business Central endpoint.

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