...
Journal - labor and expense accounting details
Accounts Payable - expense accounting, vendor payables
Project/Job Journal - labor and expense project accounting details
D365 BC Apps, Plugins and Extensions
The D365 BC marketplaceAppSource 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:
...
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:
...
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.
...
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.
Asynchronous service is also offered.
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
D365 BC Field | DATABASICS Data field |
|
No. | EMPLY_ID | Primary key |
Name | N_FIRST | First Name |
Name | N_LAST | Last Name |
Resource Group | DEPT_CODE | Home Cost Center |
EMAIL1 | Used for login and notifications | |
Employment Date | START_DATE | Used for access control, as well as tenure based logic for leave management if applicable |
Termination Date | END_DATE | Used for access control, as well as foundation for final balance reporting for leave management if applicable |
Data Push to DATABASICS
Flat files can be imported into DATABASICS from a dedicated SFTP site: more information here
...
Connecting To Dynamics 365 Business Central
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.
OData Service URL — The address of any acceptable URL where the Dynamics 365 Business Central / NAVOData service is located.
User — The name of the user who has rights to access Dynamics 365 Business Central / NAVOData, if your Dynamics 365 Business Central / NAVOData service requires authentication.
Password — The password, if your Dynamics NAVOData service requires authentication.
Note: If you are connecting to Dynamics 365 Business Central, you must enter your Web Service Access Key in the Password field NOT your password.
Company Name — Name of the Dynamics 365 Business Central / NAV Company to access. This field is optional. If left blank, Dynamics 365 Business Central / NAV returns the default company.
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.
Note: Connection property names are case-sensitive.
Name | Data Type | Required | Secured | Usage |
|---|---|---|---|---|
ServiceUrl | string | Yes | No |
|
User | string | No | No |
|
Password | string | No | Yes |
|
AuthenticationType | string | Yes | No | None,Basic |
CompanyID | string | No | No |
|
D365 Business Central References
D365 Business Central API Reference - API(V2.0) for Dynamics 365 Business Central - Business Central | Microsoft Docs
D365 Business Central Web Services Guide - SOAP and ODATA Web Services - Business Central | Microsoft Docs
D365 Business Central File import Guide - Use Excel to import data into Business Central - Business Central | Microsoft Docs