...
Journal - labor and expense accounting details
Vendor Invoice Journal - expense accounting, vendor payables
D365 Finance Plugins and Extensions
The D365 AppSource offers many functionality and industry specific plug-ins and extensions. These can add value for integration purposes, and DATABASICS works with customers to allow leveraging this enhanced functionality in support of their requirements.
The integrations will be similar to what is outlined here, but with adjustments made to facilitate for the customer’s and the specific plugin’s or extension’s requirements, including enhanced process functionality and custom fields / dimensions.
Integration methods
Data flow inbound to and outbound from DATABASICS is managed using the DATABASICS Import / Export utility.
...
Register your application with Azure AD — For instructions, see Register a native application with AAD in the Service Endpoints section of the Dynamics 365 For Operations / AX online documentation.
Obtain an authentication URL — You can either use a standard URL or specify an endpoint:
Standard URL — Use the standard Microsoft URL: https://login.microsoftonline.com/common.
Specify an endpoint — Use an endpoint specific to the user who has access to the Dynamics 365 For Operations / AX application. For example, if John Doe has access to the application, and his email address is john.doe@companyname.com, the Azure AD domain name would be companyname.com.
For more information on authentication with Azure AD, see Basics of Registering an Application in Azure AD.
Connecting To Dynamics 365
...
Finance
This section provides information on creating a Integration - Connect Connection an online Connection to Dynamics 365 For OperationsFinance.
Select Connections from the menu.
From the Connections page select Create to open the Create a connection dialog.
Select the Connector from the list to open the Connection dialog, and then enter the following information for this Connection:
Name — This can be any meaningful name, up to 25 characters.
Alias — An alias for this Connection name. The alias is generated from the Connection name, and can be up to 25 characters. The Connection alias can include letters, numbers, and underscores. Spaces and special characters are not accepted. You can change the alias. For more information, see Connection Alias.
OData Service URL — The address of any acceptable URL where the OData service is located. This URL must end in /data.
User — The name of the user who has rights to access OData, if your OData service requires authentication. Required.
Password — The password for User, if your OData service requires authentication. For more information on OData, see your endpoint provider. Required.
Client ID — GUID that identifies the client in the Dynamics 365 For Operations system. This is the Application ID generated when registering the application in Azure Active Directory. Required.
Authentication URL — The URL where the Client ID is verified in following the format. Required.
http://login.microsoftonline.com/[domain_name]
Company Name — The company specified in Dynamics 365 For Operations for this integration. Required.
Select Test to ensure that the agent can connect to your database. Be sure to test the Connection against all agents that use this Connection.
Select OK to save the Connection.
...