Versions Compared

Version Old Version 6 New Version 7
Changes made by

Lakshmi Manda (Deactivated)

Lakshmi Manda (Deactivated)

Saved on

Key

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

...

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

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

...

…

  1. Business Central Create

...

Share

Business Central Create

  • Kalpana MalladiImage Added
  • Lakshmi MandaImage Added

Owned by Kalpana Malladi

Last updated: just a moment ago by Lakshmi Manda

6 min read4 people viewed

 

 

In this article

Overview

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

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

...

Snap Type

The Dynamics 365 Business Central Create Snap is a Write-type Snap that creates a user in the application.

...

 Works in Ultra Pipelines. 

Limitations

None

Known Issues

...

  • The Business Central Create 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 creating, updating, or deleting operations. Learn more about the API limitations: API documentation for Business Central.

Known Issues

  • 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 is optional for a few entities, such as Subscriptions, whereas it is mandatory for the remaining entities. Therefore, if the field is left blank, the Snap displays the following error:

    Image Added

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

Snap Views

Type

Format

Number of Views

Examples of Upstream and Downstream Snaps

Description

Input 

Document

 

  • Min:

0

  • 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.

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 to 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: Business Central Create
Example: BC Create

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: 

Cronus

My Company

String/Expression/

Suggestion

Suggestions

Specify the company registered with the Business Central application.

Entity*

 

Default Value: N/A
Example:

People

Employees

String/Expression/Suggestions

Specify the OData entity object.

Batch type

Default Value: Stop-On-Error
Example: Transactional

Dropdown list

Specify the expected behavior of the batch. The following are the three batch types

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

the

  • an error.

  • Transactional: Sends all the records and the records with

error

  • 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: 

1

100
Example:

100

50

Integer/Expression

Specify the batch size to create a number of users in a batch.

Timeout (seconds)

 

Default Value: 

300

60
Example: 100

Integer/Expression

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

Number of retries

 

Default Value: 0
Example: 5

Integer/Expression

Specify the maximum number of retries 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 in seconds, the time period 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: Validate & Execute
Example: Execute only

Dropdown list

Select one of the following three Snap execution modes:

  • 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

More than 6000 requests were made in 300 seconds.

You must decrease

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

All Snaps related to the Microsoft

Dynamics 365 For Sales

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

Reason phrase = BAD REQUEST, refer to the error_entity field in the error view document for more details.

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 %).

Please check Client secret is expired

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

{"http_status_code": 500, "response_map": {"error_list": [{"message": "Request to token endpoint Sign in to your account failed for account \"/Tenantidshared/Azure Sharepoint Account\" of type \"SharePoint Online Account\""}]}}

The Client secret or Client Id are not valid.

Generate new Client secret.

Error 401

Token is invalid

Provide a valid token and reauthorize the account.

Examples

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

...

Download this pipeline.

Step 1: Configure the Mapper Snap with the different fields you want to add to the record.

...

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

Image Removed
Image AddedImage Modified

Step 3: Configure the Mapper Snap with the fields that you want to update for a specific ID.

...

Step 4: Configure the Primary Key in the Business Central Update Snap when the ID populates in the field. On validation, the output shows the updated record.

Image Removed
Image Added

Image Modified

Step 5: Configure the Primary Key in the Business Central Read Snap. On validation, the Snap reads the record from the application and displays the information in the output view.

Image Removed
Image Added

Image Removed
Image Added

Step 6: Configure the Primary Key in the Business Central Delete Snap when the ID populates in the field. The record is deleted on validation, and the success message is displayed in the output view.

Image Removed
Image Added

Image Removed
Image Added

Downloads

Info

  1. Download and import the Pipeline into SnapLogic.

  2. Configure Snap accounts, as applicable.

  3. Provide Pipeline parameters, as applicable.

...