Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

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 Finance and is imported to DATABASICS to support valid data in the outbound flows.

Organization Structure

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

  • Email address

  • Manager ID - supporting approval requirements if included

  • Hire Date

  • Termination Date

Work Breakdown Structure

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

  • Manager ID - supporting approval requirements if included

  • Start Date

  • End Date

...

Integration methods

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

...

In a D365 Finance 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.

Synchronous service (OData webservices Pull)

...

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.

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

  • Email address

  • Manager ID - supporting approval requirements if included

  • Hire Date

  • Termination Date

Work Breakdown Structure

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

  • Manager ID - supporting approval requirements if included

  • Start Date

  • End Date