Microsoft Dynamics 365 Business Central - online

Microsoft Dynamics Business Central support

Overview

The document contains information about the configurations needed to connect Dynamics Mobile App with Microsoft Dynamics 365 Business Central (BC).

Dynamics Mobile provides ready add-on for Microsoft Dynamics 365 Business Central (BC).

This allows the mobile apps developed on top of Dynamics Mobile SDK to :

  • consume data originating from BC in offline mode

  • send transactions to BC

  • consume, create, update data originating from BC in online mode ( also called Livelink)

Prerequisites

  • Microsoft Dynamics Business Central instance with the following setups:

    • Activated ODATAv4 service for each, entity which needs to be consumed via Livelink

    • Activated NTLM authentication mode

    • ODATAv4 interface visible via internet from Dynamics Mobile Cloud

Configuration

Dynamics Mobile needs certain configurations to be made in order to be able to connect to Microsoft Dynamics Business Central.

The configuration for BC includes 2 main sections:

  • Live Link configuration - controls the way the mobile applicaitons consume data from BC in real-time (VAN Sales, Warehouse&Inventory, Approvals)

  • Sync configuration - controls the way the mobile applications consume data from BC for off-line mode ( VAN Sales, Surveys, Smart Trade)

If the mobile applications needs to consume on-line data via livelink, the administrator needs to activate and configure the live link. The live link configuration is provided for each user role, separately. via the User Role's Settings screen. Please consult with the following page for general information about working with User Role Settings.

Livelink for Microsoft Dynamics Business Central requires the following parameters to be provided

Parameter name

Values

Notes

type

d365bc

Must have value d365bc

authType

ntlm

The type of authentication during authentication sessions to BC. Only ntlm is currently supported.

servicePath

string

The path portion of the URL used to connect to BC.

MyBCInstancePath/ODataV4

host

string

The name of the host (internet name) where the instance is visible via internet. It may be DNS name or IP address

bc.mycompany.com

port

number

the TCP port where the BC service is published

protocol

http or https

The protocol used to communicate with the instance. Supported are http or https.

userName

string

The username from BC used by Dynamics Mobile to authenticate against BC

password

string

The password from BC used by Dynamics Mobile to authenticate against BC

workstation

string

Name of the workstation ( machine name) used for NTLM authentication purposes

domain

string

Name of the windows domain used for NTLM authentication purposes

The format of the setting in the User Role, requires the settings to be wrapped in an object property with name liveLinkService_[MYNAME] , where NAME is arbitrary name dependent on the actual mobile or backend application.

The following example configures a service called warehouseService.

It will allow the mobile devices to use livelink configuration called "warehouseService"

{
"language": "en",
....
"liveLinkService_warehouseService": {
"type":"d365bc",
"authType":"ntlm",
"servicePath":"MyBCService/ODATAAv4",
"host":"bc.mycompany.com",
"port":"7581",
"protocol":"http",
"userName":"myuser",
"password":"123",
"workstation":"myservermachinename",
"domain":"mydomain"
}
...
}

Sync connection activation

The mobile apps which needs to consume and send offline data from Microsoft Dynamics Business Central need to have a "syncMethod" setting in the User Role of the mobile users who needs it.

The syncMethod has the following attributes (same as for livelink):

Parameter name

Values

Notes

type

d365bc

Must have value d365bc

authType

ntlm

The type of authentication during authentication sessions to BC. Only ntlm is currently supported.

servicePath

string

The path portion of the URL used to connect to BC.

MyBCInstancePath/ODataV4

host

string

The name of the host (internet name) where the instance is visible via internet. It may be DNS name or IP address

bc.mycompany.com

port

number

the TCP port where the BC service is published

protocol

http or https

The protocol used to communicate with the instance. Supported are http or https.

userName

string

The username from BC used by Dynamics Mobile to authenticate against BC

password

string

The password from BC used by Dynamics Mobile to authenticate against BC

workstation

string

Name of the workstation ( machine name) used for NTLM authentication purposes

domain

string

Name of the windows domain used for NTLM authentication purposes

Settings example

The format of the setting in the User Role, requires the settings to be wrapped in an object property with name liveLinkService_[MYNAME] , where NAME is arbitrary name dependent on the actual mobile or backend application.

The following example configures a service called warehouseService.

It will allow the mobile devices to consume offline data from BC.

{
"language": "en",
....
"syncMethod": {
"type":"d365bc",
"authType":"ntlm",
"servicePath":"MyBCService/ODATAAv4",
"host":"bc.mycompany.com",
"port":"7581",
"protocol":"http",
"userName":"myuser",
"password":"123",
"workstation":"myservermachinename",
"domain":"mydomain"
}
...
}

See also