Overview
This guide provides instructions on setting up Recurring Integrations for D365 F&O (Cloud) with the necessary data that AGR requires. Recurring Integrations builds on data entities and the Data management framework and enables the data transfer between F&O and third-party services or applications.
Recurring Integrations uses REST API endpoints with 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 in Microsoft Entra ID (Azure AD) and give it appropriate permissions. You will need the application ID when you create and enable a recurring job. The application ID will go into the System admin -> azure active directory screen and on the recurring job.
Data Mapping
In the article AGR x D365 F&O Data Entities, you will find the complete list of Dynamics 365 Finance & Operations data entities and their corresponding fields needed by the AGR.
In the AGR Data Interface - F&O Data Mapping document (button below) you can find a description of the Standard Mapping from D365 F&O into AGR via the AGR Data Interface.
If you need customizations to the data mapping to fit your needs, this can often be accommodated at a cost.
Instructions
Create a Data Project
From the main F&O dashboard, navigate to Workspaces and select Data management.
Choose Export to create a new data export project.
Choose a descriptive job name, and ensure the data source corresponds to the entities and fields detailed in AGR x D365 F&O Data Entities.
Upload a data file for the entities. Make sure that each entity is added, and that no errors occur.
Create a Recurring Data Job
Open Data management, locate your project, and select Create recurring data job.
Enter a job name and a description.
In Setup authorization policy, enter the Application (client) ID from Azure AD (created in the Overview)
In Advanced Options choose files.
The job should run daily at end of business day.
Give AGR Access to the Imported Files
In Manage -> Manage recurring data jobs, note the job’s unique ID, AGR needs it.
AGR needs the URL. https://<base URL>/api/connector/enqueue/<ID>?
AGR needs application id, secret value and tenant id of the app created in Overview.
AGR needs the resource or F&O base URL (e.g.,
https://company.operations.dynamics.com).