Dynamics 365 Configuration
The integration requires a collection of OData Web Service “endpoints” to be exposed in order to function. OData is a web service protocol that allows the integration to read and write data to the Dynamics 365 database and must be activated using the Dynamics 365 Administration tool.
Exposing OData Endpoints
Dynamics 365 must have the following list of endpoints exposed. In the Dynamics 365 client the Web Services interface can be opened byOdata in the top search field and clicking Web Services under Lists.
Create a new “Page” Object Type for each Object ID in the following table and ensure that each new entry has the Published column checked. The Object Name represents the interface to be exposed. The Service Name can be any URL safe value that represents the interface being exposed. Each defined Service Name should be unique to the Object Name.
OData Endpoint Entry Example
The following screenshot illustrates an example entry for Object ID 43, Sales Invoice.
The Service Name of “ARInvoice” will be applied to the OData URL upon publishing. Confirm that the OData Web Service is working by navigating to the OData URL in your browser.
Additional OData Configuration
Certain Dynamics 365 extensions or configurations may prevent the integration from successfully importing data to certain OData Pages. You can update (or “Design”) Pages in Dynamics 365 manually through the Sandbox environment, and then publish them into your Production environment, or you can request a custom extension to fix identified out-of-the-box issues. (See Customizations.)
To manually Design changes to a Page, navigate to the desired Page in the Dynamics 365 sandbox environment, click the cog in the upper right, and click Design. In this example, we’re going to add “External Document No” to the General Ledger Entries Page.
When Design mode initializes, click More > Field
A sidebar will open to the right with all the available fields the Page can contain. Search for the field to be added, then click and drag the field onto the Page in the desired location.
After the field loads into the Page, click Stop designing. You will be required to publish the changes, providing values for Extension Name and Publisher. Be sure to select the Download Code checkbox so that the published extension can be uploaded into your production environment. Click Save after inputting the required values to download the published extension.
Dynamics Web Service Access
You will need to enable a Web Service Access Key for the Dynamics User that will be used to authenticate with the Dynamics web services. Open up the User Card for the desired Dynamics User and click the ellipsis on Web Service Access to generate a key.