Dynamics 365 Business Central

The DATABASICS Time & Expense Reporting system integrates to Dynamics 365 Business Central (D365 BC) to support time and expense accounting.

Each D365 BC entry module specific outbound specification from DATABASICS is outlined in separate sub-sections, as follows:

• Journal - labor and expense accounting details

• Accounts Payable - expense accounting, vendor payables

• Project/Job Journal - labor and expense project accounting details

D365 BC Plugins and Extensions

The D365 BC marketplace 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.

Inbound Data to DATABASICS

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

Organization Structure

In a D365 BC 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

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

• Email address

• Manager ID - supporting approval requirements if included

• Hire Date

• Termination Date

Work Breakdown Structure

In a D365 BC 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

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

• Manager ID - supporting approval requirements if included

• Start Date

• End Date

Inbound Integration methods

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

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

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

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

Data Push to DATABASICS

Flat files can be imported into DATABASICS from a dedicated SFTP site: more information here

Files must be provided according to agreed specifications, loads can be scheduled according to requirement (e.g. weekly, daily, hourly), or manually triggered on an as needed basis.