As I promised in my previous post Microsoft Dynamics 365 for Operations – Warehousing, in this post I would like to share my experiment in configuring Microsoft Dynamics 365 for Operation – Warehousing to connect to a Dynamics 365 for Operations instance.
In this post I ‘d like to describe how I setup everything from scratch.
Let’s start. You will need the following pre-requisites:
- Office365 account. Purpose: To create LCS project and deploy Dynamics 365 for Operations instance.
- Azure subscription for Office 365 account. Purpose: To register application for Warehousing. Keep in mind, without Office 365 account subscription you will not be able to select Microsoft Dynamics ERP application.
- We need the latest version of Dynamics 365 for Operation. If you are not an administrator of your tenant it would be better to create your own admin account. To do this you need to follow the steps below to deploy the latest version of Dynamics 365 for Operation:
- Personal e-mail account
- Created Microsoft ID account using the email account
- Azure subscription for Microsoft ID account
- Created new project under Office365 account and connected to Azure account with full permissions
- Deployed Dynamics 365 for Operation Update 7 under Office 365 account and admin azure subscription
This is all for pre-requisites.
Now we can jump to the configuration related to our Microsoft Dynamics 365 for Operation – Warehousing itself.
To perform the steps below I used the link: https://docs.microsoft.com/en-us/dynamics365/unified-operations/supply-chain/warehousing/install-configure-warehousing-app.
First off, we need to create a web service application in Azure Active Directory (pre-requisites step 2).
Web service application in Azure Active Directory
Navigate to https://manage.windowsazure.com.
Enter the name and password for the user who has access to the Azure subscription (pre-requisites step 2).
In Azure Portal, in the left navigation pane, click Active Directory.
In the grid, select the Active Directory instance.
On the top toolbar, click Applications.
In the bottom pane, click Add. The Add application wizard starts.
Enter a name for the application and select Web application and/or web API.
Enter the sign-on URL, which is your web app URL (pre-requisites step 5). I entered the following:
Enter the App ID URI. I entered the following:
Go to the Configure tab.
Scroll down until you see the Permissions to other applications section. Click Add application
Select Microsoft Dynamics ERP in the list. Click the Complete check button in the right corner of the page. Note: If you do not see Microsoft Dynamics ERP application, see pre-requisites 2.
In the Delegate Permissions list, select all the check boxes. Click Save.
Make a note of the following information:
Client ID – As you scroll up the page, you will see Client ID displayed.
Key – In the Keys section, create a key by selecting duration, and copy the key. This key will later be referred to as the Client secret.
Key will be visible once you press Save button.
Next step is to configure a user account in Dynamics 365. Follow the steps below.
Create and configure a user account in Dynamics 365
Go to System administration > Common > Users.
Assign the Warehouse mobile device user role to the user by clicking Assign roles button.
Additional setup is to link AAD to Warehousing App. Follow the steps below.
Associate your Azure Active Directory application with the warehousing app user.
Go to System administration > Setup > Azure Active Directory applications.
Configure warehouse worker
Go to Warehouse management > Setup > Worker
Select user ID and click Reset password. After that you can set your own password.
Verify Mobile device menu
Go to Warehouse management > Setup > Mobile device > Mobile device menu
Configure the Warehousing application on your phone
In my post I used Android version 7.0
In the app, go to Connection settings.
Clear the Demo mode field
- Azure Active directory client ID – The client ID is obtained in step 13 in “Create a web service application in Active Directory”. Follow the step “Web service application in Azure Active Directory” in this post to find out your Client ID.
- Azure Active directory client secret – The client secret is obtained in step 13 in “Create a web service application in Active Directory”. Follow the step “Web service application in Azure Active Directory” in this post to find out your Key.
- Azure Active directory resource – The Azure AD directory resource depicts the Finance and Operations root URL. Note: Do not end this field with a forward slash character (/). This is URL to your Dynamics365 application. For example: https://o365c67a54d218c24cadaos.cloudax.dynamics.com
- Azure Active directory tenant – The Azure AD directory tenant used with the Finance and Operations server: https://login.windows.net/your-AD-tenant-ID. For example: https://login.windows.net/enavate.onmicrosoft.com. Note: Do not end this field with a forward slash character (/). To find out your tenant go to portal.azure.com and navigate to your user info. You will see the Directory You can use the following link to verify if your tenant is right https://login.windows.net/enavate.onmicrosoft.com/.well-known/openid-configuration
- Company – Enter the legal entity in Finance and Operations to which you want the application to connect. In my case I selected USMF company
Select the Back button in the top-left corner of the application. The application will now connect to your Dynamics 365 server and the log-in screen for the warehouse worker will display.
Enter User ID and Password (Follow the step “Configure warehouse worker” in this post to find out User ID and Password).
Press green button. You will be presented with the Main menu screen
Verify Inbound menu
Go back and check About. On the about page you can see that URL to your Dynamics 365 instance
That’s all! I hope you will find it beneficial.