Content Comparison

...

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 properties / dimensions.

For more information about Business Central integrations please visit Integration between Finance and Operations apps and third-party services - Finance & Operations | Dynamics 365 | Microsoft Docs

Integration methods

Data flow inbound to and outbound from DATABASICS is managed using the DATABASICS Import / Export utility.

...

• Employee ID

• Vendor ID

• Employee First and Last Name

• Home Company

• Employee Type - supporting entry validation (e.g. OT) if included

• Default Labor Category / Class

• Email address

• Manager ID - supporting approval requirements if included

• Hire Date

• Termination Date

...

• Customer

• Job / Project

• Task

• Work Order

• Global / Custom Dimensions

• Bill Rate - supporting billing, if included

The dimensions utilized, in turn may have attributes and properties supporting customer’s specific requirements that can also form part of the DATABASICS data set, including:

• Project / Task Type

• Owning Company

• Resource Assignment

• Assigned Labor Category / Class

• Manager ID - supporting approval requirements if included

• Start Date

• End Date

...

Example employee profile specification, with exposed fields on link: https://api.businesscentral.dynamics.com/<version_and_URLid>/ODataV4/Company('<Company_ID>')/Resource_Card

Azure Active Directory

Azure Active Directory (Azure AD), a Microsoft multi-tenant, cloud-based directory and identity management service, provides single sign-on (SSO) access to cloud SaaS Applications, such as Office365. To begin, set the client ID in the Azure AD account where the Dynamics 365 For Operations Connector is deployed.

...

1. Select Connections from the menu.

2. From the Connections page select Create  to open the Create a connection dialog.

3. Select the Connector from the list to open the Connection dialog, and then enter the following information for this Connection:
   

   Image Added

   • 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 Finance 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 Finance for this integration. Required.

4. 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.

5. Select OK to save the Connection.

Note: Connection property names are case-sensitive.