Dynamics 365 Finance

(aka Microsoft Dynamics 365 for Operations, Microsoft Dynamics for Finance and Operations)

The DATABASICS Time & Expense Reporting system integrates to Dynamics 365 Finance to support time and expense accounting.

Supporting the D365 Finance set-up, integration data can be read directly from and written to exposed pages and fields as defined by the customer using Open Data Protocol (ODATA) webservice. DATABASICS supports specific D365 Finance entry modules, including:

• General Ledger - posting labor and expense accounting details according to your established chart of accounts

• Vendor Invoice Journal - posting invoice data into accounts payable

• Expense Report Entry - using DATABASICS enhanced functionality to post in D365 Finance’s simplified entry

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

Open

In a D365 Finance integration data can be read directly from and written to exposed pages and fields as defined by the customer using Open Data Protocol (ODATA) webservice. Alternatively, the customer can provide flat files with data, according to agreed specifications.

Inbound Data to DATABASICS

In a bi-directional integration Demographic (Organization) and Project (WBS) data typically originates in D365 Finance and is imported to DATABASICS to support valid data in the outbound flows.

The loads will validate to make sure all the required fields are provided in order for the data elements to be active in DATABASICS.

Organization Structure

In a D365 integration the DATABASICS Organization structure is mapped to the demographic dimensions utilized by the customer, typically consisting of one or more of the following:

• Company

• Location

• Resource Group

• Vendors - supporting reimbursement through Accounts Payable if included

• Cost Rates - supporting project cost accounting solution if included

• Employee / Resource

The Employee typically has one or more of the following properties:

• 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

Work Breakdown Structure

In a D365 integration the DATABASICS Work Break Down Structure is mapped to the activity dimensions utilized by the customer typically consists of one or more of the following:

• 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

Synchronous service (OData webservices Pull)

We can use the DATABASICS import / export utility to read data directly from exposed pages and field as identified by the customer. Using the direct pull solution provides the organization and project data, and refreshes the data in DATABASICS for new records and existing records without the need for an intermediary step.

An agreed specification will outline what data to import from where, mapping the D365 Finance data to DATABASICS.

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.

To set the client ID in the Azure AD account, you must:

• Register your application with Azure AD — For instructions, see Register a native application with AAD in the Service Endpoints section of the Dynamics 365 Finance 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 Finance 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 an online Connection to Dynamics 365 Finance.

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:
   
   

   Open

   

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