Microsoft Dynamics 365 Integration

About integrating DSI Platform with Microsoft Dynamics 365

Beginning in 9.0 SP10, DSI Platform supports integration with Microsoft Dynamics 365. By integrating DSI Platform with Microsoft Dynamics 365, you can allow your DSI apps to read from and write to applicable records in Microsoft Dynamics in order to maintain a unified, accurate system of record.

The Microsoft Dynamics 365 Connector uses Azure Active Directory authentication. Before ScanWorkX and Microsoft Dynamics 365 can communicate, you must establish permissions within Azure Active Directory. For more information, refer to Integrate DSI Platform with Microsoft Dynamics 365 Overview.

Integrate DSI Platform with Microsoft Dynamics 365 Overview

You can integrate Microsoft Dynamics 365 to DSI Platform SP10 or later.

To integrate your DSI Platform instance and an instance of Microsoft Dynamics, complete the following procedures.

Integrate DSI Platform with Microsoft Dynamics 365

To integrate DSI Platform with Microsoft Dynamics 365, complete the following steps in Azure Active Directory.

In a web browser, go to https://portal.azure.com and log in to the Azure management portal.
In the left pane, select Azure Active Directory.
In the center pane, select App registrations.
In the right pane, select New application registration.
In the center pane, under Create, complete the following steps.
1. For Name, enter the name of the application.
  
  Step Information
  
  Note: To avoid confusion, it is recommended that you give your app the same name as the Dynamics 365 for Operations server.
2. For Application type, select Native.
3. For Sign-on URL, enter the Dynamics 365 for Operations server path.
  
  Example
  Example: https://YOURSERVER.cloudax.dynamics.com/services/ScanWorkX_Service.
4. Select Create.
On the App registrations tab, select the app you created and copy or write down the Application ID for later use in this procedure.
Select Settings > Required Permissions > Add.
Select Windows Azure Active Directory and verify that the following settings are set to No.
Step Information
- Sign in and read user profile
- Read all users' basic profiles
- Access the directory as the signed-in user
Select Save.
Under Required permissions, select Add.
Under Add API access, select Select an API.
Under Select an API, select Microsoft Dynamics ERP (Microsoft.ERP) > Select.
Under Enable Access, enable the following settings to allow DSI Platform to access the functions.
Step Information
- Access Dynamics AX online as organization users
- Access Dynamics AX data
- Access Dynamics AX Custom Service
Select Select > Done.
Under Required Permissions, select Grant Permissions.
Review the permissions information and select Yes.

About connectors

Connectors are specialized components that register APIs in Mobile Enterprise Platform, and provide communication with a range of third-party systems.

All connector types allow your app developers to easily register any source API call within the system of record. Developers can then easily leverage source system functionality within their apps without knowing the specifics of how communication with each ERP system is performed. Advanced Inventory continually updates these interfaces, in conjunction with major ERP releases, so that as your system adds functionality and updates features, your Advanced Inventory system can keep pace.

You can configure the following connectors in Mobile Enterprise Platform to enable communication between Mobile Enterprise Platform and the specified enterprise software. If the system interfaces with multiple enterprise environments, the environment for which to configure the enterprise connector must also be selected.

EnterpriseOne Web Connector

Enables the Advanced Inventory MASP to register any JDE business function that is published as a Web service on the Oracle Business Services Server (BSSV).

EnterpriseOne XML Connector

Enables the MASP to register and call any JDE business function available in the system. This connector leverages the E1 Interoperability Client, using XML to send and receive API requests between the MASP and the E1 Enterprise/Application server.

Procedure Connector for Oracle

Enables you to register and call any PL-SQL package within the Oracle Database, assuming the registering user has read and execute authority to the PL-SQL package and associated tables.

Lawson Connector

Enables you to register and call any Lawson API through the Movex or M3 Enterprise Management System, assuming the registering user has authority to read and execute the APIs within the management system.

Microsoft Dynamics 365 Connector

Enables communication with Microsoft Dynamics 365.

Microsoft Dynamics AX Connector

Enables communication with Microsoft Dynamics AX.

Oracle Web Services Connector

Enables communication with the Oracle Application Integration Architecture, which integrates any combination of custom, Oracle, and non-Oracle applications into business processes.

SAP .NET Connector

Enables you to register and call any SAP BAPI on the SAP Application Server, assuming the registering user has the appropriate authority in the SAP System.

Webservices Connector

Enables communications with external systems via SOAP and REST web service APIs. With this connector, you can define web service definitions that leverage public API providers such as Google Maps and Weather Underground within a Mobile Enterprise Platform app.

TIMETrac Connector

Receives transactions from time clocks and other devices and moves them to TIMETrac using the TIMETrac web service.

Configure the Microsoft Dynamics 365 Connector

The Microsoft Dynamics 365 Connector transmits data among components and the Microsoft Dynamics 365 enterprise software.

Prerequisite: To configure this connector, Microsoft Dynamics 365, Azure Active Directory, and ScanworkX Server must already be installed. Additionally, the required licenses must be installed.

To configure the Microsoft Dynamics 365 Connector, complete the following steps in DSI Platform Manager.

Go to Admin > Configuration > Connector Settings page.
From the list of connectors, select Microsoft Dynamics 365 Connector.
For Dynamics 365 Url, enter the url for Dynamics 365.
For Dynamics 365 Username, enter the name of the user who will use Dynamics 365.
For Dynamics 365 Password, enter the password for the username you specified.
For Azure Active Directory Resource, enter the Azure Active Directory URI.
For Azure Active Directory Tenant, enter the Office 365 tenant ID.
For Azure Active Directory Client App ID, enter the Active Directory Client ID.
For ScanWorkX host name, enter the name or IP address of the computer hosting the system to which requests are sent.

Step Information

Note:This value must be specified based on the particular configuration.
For ScanWorkX port, enter the network port on which the host computer communicates with the server.
Step Information
Note:

This port number is specified in the ScanWorkX install.

The default port number is 20001.
To specify that request/response documents are logged, select Log request/response documents.

Step Information

Note:This is a unique transaction ID. The logs are located in the Logging folder in the installation.
For Time-out (sec), enter the amount of time (in seconds) to wait for a reply from the web service when sending a request.
Step Information
Note:

A default value is provided and can be changed.

The time-out range can be from 5 to 300 seconds.
Select Save.

Register Microsoft Dynamics 365 functions

Registering functions provides access to the functions to be called in apps. A function can be registered any time before you create an app that uses that function.

Prerequisite: Before registering a Microsoft Dynamics 365 function, the Microsoft Dynamics 365 connector must have been configured. Refer to Configure the Microsoft Dynamics 365 Connector.

To register a function to the Microsoft Dynamics 365 connector, complete the following steps in DSI Platform Manager.

Go to Develop > Connectors.
Select Microsoft Dynamics 365 Connector.
On the Registered Functions page, select the functions you want to register and select Finish.
On the Select Functions page, for Components, specify a component name.
Select Next.
For Select Components, select the functions to register and select Finish.
Select Done.

Postrequisite: After a function is registered, it can be tested using the Test tool for that function on the Registered Functions page. Refer to Test functions.

There was a problem loading this topic