Recurring integrations

This article provides information about recurring integrations. The process of data migration, and movement into and out of any enterprise system, is a critical piece that any platform must support.

The process of data migration, and movement into and out of any enterprise system, is a critical piece that any platform must support. Considerable effort and planning go into building third-party integrations between an enterprise line of business (LOB) system such as Microsoft Dynamics 365 for Finance and Operations, Enterprise edition and various source systems. Microsoft Dynamics AX 2012 enables these scenarios through Application Integration Framework (AIF). For Finance and Operations, we have tried to simplify this process for all parties who are involved, from integration solution builders to customer end users.


Integration does the following:

  • It builds on data entities and the rich data management platform (Data Import/Export Framework [DIXF]).
  • It enables the exchange of documents/files between Finance and Operations and any third-party application or service.
  • It supports several document formats, source mapping, Extensible Stylesheet Language Transformations (XSLT), and filters. Formats
  • It uses secure REST application programming interfaces (APIs) and authorization mechanisms to receive data from and send data back to integration systems. REST

Authorization for the integration REST API

The integration REST API uses the same OAuth 2.0 authentication model as the other service endpoints. Before the integrating client application can consume this endpoint, you must create an application ID in Microsoft Azure Active Directory (AAD) and give it appropriate permission to Finance and Operations. When you create and enable a recurring job, you'll be prompted to enter the AAD application ID that will be interacting with that recurring job. Therefore, be sure to note down the application ID.

Set up a data project and recurring data jobs

Create a data project

  1. On the main dashboard, click the Data management tile to open the data management workspace.
  2. Click the Import or Export tile to create a new data project. Note: If you have an existing data project, click Load project on any data project card on the Data projects tab.
  3. Enter a valid job name, data source, and entity name.
  4. Upload a data file for one or more entities. Make sure that each entity is added, and that no errors occur. Note: You can click each entity data card to set up, review, or modify field maps, and to set up XSLT-based transforms that must be applied to inbound data. For export data projects, the entity card also shows a filter link, so that you can set up filters to filter out data. Currently, all recurring data jobs in a data project use the same filter.
  5. Click Save.

Create a recurring data job

  1. On the Data project page, click Create recurring data job.
  2. Enter a valid name and a description for the recurring data job.
  3. On the Set up authorization policy tab, enter the application ID that was generated for your application, and mark it as enabled.
  4. Expand Advanced options, and specify either File or Data package.

    • Specify File to indicate that your external integration will push individual files for processing via this recurring data job. In this case, the format of the file that is expected is the same as the format that was specified when the entity was added to the data project.
    • Specify Data package to indicate that you can push only data package files for processing. A data package is a new format for submitting multiple data files as a single unit that can be used in integration jobs.
  5. Click Set processing recurrence, and set a valid recurrence for your data job. Processing recurrent

  6. Optional: Click Set monitoring recurrence, and provide a monitoring recurrence. Note: Currently, the monitoring recurrence enables load monitoring only on your recurring data job queue. No additional policies are supported via this service. You can use this feature to fine-tune the processing recurrence as required by load demand.
  7. Click OK, and then click Yes in the confirmation dialog box.

Manage recurring data jobs

Open the System Administration workspace (not module) and click the Data Management IT tile. Data management workspace In this workspace, on the Recurring data job tab, click the recurring job to view more details for. The Management page contains a grid that lists any messages that are waiting in the queue. This view helps you monitor messages and processing status. Management page

Submitting data to recurring data jobs

You can use well-known integration REST endpoints to integrate with the client, submit documents (import), or poll available documents for download (export). These endpoints support OAuth.

Integration REST APIs

The following set of APIs is used to exchange data between the integration client and Finance and Operations.

For import (enqueue)

Make an HTTP POST call against the following URL.

https://<baseurl>/api/connector/enqueue/<activity id>?entity=<entity name>

In the message body, you can the pass the data as a memory stream. Example


To get the activity ID, go to the manage recurring job view, and copy and paste the GUID (highlighted in the following screen shot). Manage recurring job

For export (dequeue)

To return a data package that contains all the data entities that were defined in that data project, and that the client application can unzip and consume, use the following structure.

https://<baseurl>/api/connector/enqueue/<activity id>



After the client downloads the data, an acknowledgment must be sent back to Finance and Operations, so that we can mark the data as received.

For acknowledging

Use the API.

https://<baseurl>/api/connector/ack/<activity id>