Dynamics 365 Finance and SCM Bulk Export
In this article
Overview
You can use this Snap to export the data associated with a selected entity (in bulk) from the Microsoft Dynamics 365 Finance and SCM application.
Snap Type
The Dynamics 365 Finance and SCM Bulk Export Snap is a Read-type Snap.
Prerequisites
A valid account with the required permissions.
 You should create an export project in the Finance and Operations application prior to calling the APIs.
Support for Ultra Pipelines
Works in Ultra Pipelines.Â
Known Issues
None.
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 Binary  |
|
| Sends the new user information in bulk 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 in 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 | Field Dependency | Description |
---|---|---|---|
Label* Â Default Value:Â Dynamics 365 Finance and SCM Bulk Export | String | N/A | 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. Â |
Integration type  Default Value: DMF package API | Dropdown list | N/A | Specify the type of import API. The available options are:
|
Operation Default Value:Â Trigger Export | Dropdown list | Appears when the Integration type is DMF package API. | Select one of the operations. The available options are:
|
Package name Default Value:Â N/A | String/Expression | Appears when the Operation is Trigger Export or Trigger And Generate Export. | Specify the name of the exported data package. This field is mandatory when you select Trigger Export as the Operation. |
Definition group ID Default Value:Â N/A | String/Expression | Appears when Operation is Trigger Export or Trigger And Generate Export. | Specify the name of the export data project. |
Execution ID Default Value:Â None | String/Expression | Appears when Operation is Generate Export. | Specify the ID to use for the bulk export job. |
Legal entity Default Value:Â N/A | String/Expression/Suggestion | Appears when Operation is -Trigger Export or Trigger And Generate Export. | Specify the legal entity for data export. |
Activity ID Default Value:Â N/A | String/Expression | Appears when Integration type is - Recurring integrations API. | Specify the activity ID. Learn more about how to obtain the activity ID: https://learn.microsoft.com/en-us/dynamics365/fin-ops-core/dev-itpro/data-entities/recurring-integrations#manage-recurring-data-jobs |
Job status check interval (seconds) Default Value:Â 5 | Integer/Expression | Appears when Operation is - Generate Export or Trigger And Generate Export. | Specify the amount of time between job status check requests. |
Timeout (seconds) Default Value:Â 60 Example: 100 | Integer/Expression | N/A | Specify the connection and response timeout for the requests made to the server. |
Number of retries Default Value:Â 0 Example: 5 | Integer/Expression | N/A | Specify the maximum number of retry attempts between failures. |
Retry interval (seconds) Default Value:Â 1 Example: 10 | Integer/Expression | N/A | Specify the amount of time between retry attempts. |
Snap Execution Default Value:Â Validate & Execute | Dropdown list | N/A | Select one of the following three modes in which the Snap executes:
|
Troubleshooting
Error | Reason | Resolution |
---|---|---|
| Document/Binary output view is not enabled. | Ensure to enable the document/binary output view. |
| 401: Unauthorized | Ensure that the specified account is valid and retry. |
| Exceeded 100 check API calls. | Adjust the job status check interval for long-running jobs and retry. |
Examples
Export files from Finance and Operations application using DMF Package API
This example pipeline below demonstrates how to export the files in bulk from the Finance and Operations application.
Step 1: Configure the Dynamics 365 Finance and SCM Bulk Export Snap with DMF Package API as the Integration type and Trigger Export as the Operation to initiate the bulk export job.
Step 2: Configure the Dynamics 365 Finance and SCM Bulk Export Snap with Package name, Definition group ID, and Legal entity fields which are mandatory to configure for Trigger Export operation.
Step 3: Configure the Mapper Snap with the value from the upstream Snap to pass as the Execution ID to the downstream Snap to generate the export.
 |  |
Step 4: Configure the downstream Dynamics 365 Finance and SCM Bulk Export Snap with Generate Export as the Operation as follows:
Step 5: Validate the pipeline. On validation, the export is successful and the Snap displays the exported information in the binary output view.
Alternatively, you can use the Trigger and Generate Export as the Operation in the Dynamics 365 Finance and SCM Bulk Export Snap.
 |  |
Export files from Finance and Operations application using Recurring Integrations API
This example pipeline below demonstrates how to export the files in bulk from the Finance and Operations application using the Recurring integrations API. You must use the Recurring integration API when you want to perform a recurring data job.
Step 1: Configure the Integration type as Recurring integrations API in the Dynamic 365 Finance and SCM Bulk Export Snap.
Step 2: Configure the Activity ID, which is the mandatory field for this integration type.
Step 3: Validate the pipeline. On validation, the export job completion status is displayed with the activity ID.
Â
Downloads
Â