Versions Compared

Version Old Version 17 New Version 18
Changes made by

Lakshmi Manda

Lakshmi Manda

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Table of Contents
minLevel1
maxLevel2
absoluteUrltrue

Overview

You can use the Dynamics 365 Business Central Create Snap to create records in the Business Central application for a specific entity.

...

  • Business Central metadata does not contain information about required fields. Therefore, the Mapper Snap upstream to the Business Central Create Snap does not display the mandatory fields (showing *) in the Target Schema, which is the expected behavior.

  • The Company field in the Business Central Create Snap 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 mandatory entities where it is mandatory.

Snap Views

Type

Format

Number of Views

Examples of Upstream and Downstream Snaps

Description

Input 

Document

 

  • Min: 1

  • Max: 1

  • Mapper

Requires user data as a JSON document.

Output

Document

 

  • Min: 1

  • Max: 1

  • Mapper

  • Copy

  • Union

Writes the new user information for an entity.

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.

...

Error

Reason

Resolution

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

More than 6000 requests were made in 300 seconds.

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

Too many Requests - 429

Too many requests are sent to Microsoft Business Central endpoint.

All Snaps related to the Microsoft Business Central Snap include retry-after with <number of seconds> in the response header and automatically retry when they encounter a status 429 error. Wait for the retry to succeed.

REST API service endpoint returned error result: status code = 400

You typically receive this message when:

  • The value in the HTTP entity field is structured as an expression; but the expression toggle is off.

  • The value in the (single- or multiple-file-upload) File Key fields is inaccurate or does not contain expressions although the Expression toggle is enabled.

  • The value in the (single- or multiple-file-upload) File Name fields contains special characters, such as (&, ^, and %).

Check the values of Snap properties. Specifically:

  • Check whether your HTTP entity entry requires expressions. Update Snap settings as appropriate.

  • Check the value in the (single- or multiple-file-upload) File Key fields.

  • Check the value in the (single- or multiple-file-upload) Filename to be used fields.

Error 500

The Client secret or Client Id ID are not valid.

Generate new Client secret.

Error 401

Token is invalid.

Provide a valid token and reauthorize the account.

...

This example pipeline demonstrates how to use Business Central CRUD Snaps to create, read, update, and delete records in the application.

...

Step 2: Configure the Business Central Create Snap with the Company name that is registered with the Business Central application, the Entity, and the Batch type as followsshown. The output shows the inserted record with an ID generated automatically.

...