Input 

Document

• Min: 0

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

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

String/Expression/Suggestion

Specify the company registered with the Business Central application.

Entity*

Default Value: N/A
Example: People

String/Expression

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:

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

• Transactional: Sends all the records and the records with error to the error view.

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

Batch size

Default Value: 1
Example: 100

Integer/Expression

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

Timeout (seconds)

Default Value: 300
Example: 100

Integer

Specify the timeout to determine whether the connection is alive and also the timeout when waiting for 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.

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.

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 the batch size and retry.

Too many Requests - 429

Too many requests sent to Dynamics 365 For Sales endpoint.

All Snaps related to the Microsoft Dynamics 365 For Sales 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 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\""}]}}

Client secret is expired.

Generate new Client secret.

Error 401

Token is invalid

Provide a valid token and reauthorize the account.