Dynamics 365 Business Central Create
In this article
Overview
You can use the 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.
Prerequisites
None
Support for Ultra Pipelines
 Works in Ultra Pipelines.Â
Limitations
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 Snap is optional for a few entities, such as Subscriptions, 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.
The Microsoft Dynamics 365 Business Central Create 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  |
|
| Requires user data as a JSON document. |
Output | Document  |
|
| 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:
Learn more about Error handling in Pipelines. |
Snap Settings
Asterisk ( * ): Indicates a mandatory field.
Suggestion icon (): Indicates a list that is dynamically populated based on the configuration.
Expression icon ( ): Indicates the value is an expression (if enabled) or a static value (if disabled). Learn more about Using Expressions in SnapLogic.
Add icon ( ): Indicates that you can add fields to the field set.
Remove icon ( ): Indicates that you can remove fields from the field set.
Upload icon ( ): Indicates that you can upload files.
Field Name | Field Type | Description | |
---|---|---|---|
Label* Â Default Value:Â Business Central 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 | String/Expression/Suggestion | Specify the company registered with the Business Central application. | |
Entity* Â Default Value:Â N/A | String/Expression/Suggestion | Specify the OData entity object. | |
Batch type Default Value:Â Stop-On-Error | Dropdown list | Choose the operation you want for batching, which is applicable only when the Batch size is more than 1:
| |
Batch size  Default Value: 100 | Integer/Expression | Specify the batch size to create a number of users in a batch. | |
Timeout (seconds) Â Default Value:Â 60 | 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 | 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 | 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 | String/Expression | Specify the key for the HTTP header. | |
Value  Default Value: N/A application/json;odata.metadata=full | String/Expression | Specify the value for the HTTP header. | |
Snap Execution  Default Value: Validate & Execute | Dropdown list | Select one of the following three Snap execution modes:
|
Troubleshooting
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 |
REST API service endpoint returned error result: | You typically receive this message when:
| Check the values of Snap properties. Specifically:
|
Error 500 | 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 Snaps to create, read, update, and delete records in the application.
Step 1: Configure the Mapper Snap with the different fields you want to add to the record.
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 shown. The output shows the inserted record with an ID generated automatically.
 |
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.
 |
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.
 |
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.
 |
Downloads
Â
Snap Pack History
Â
Related Content
Â
Have feedback? Email documentation@snaplogic.com | Ask a question in the SnapLogic Community
© 2017-2024 SnapLogic, Inc.