Versions Compared

Key

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

...

  • 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

 

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

...