Install Guide

Applicable to Dynamics 365FO Version 3.13 or older.

To enable the handheld clients to be able to access the Tasklet Factory WMS SOAP based service that is hosted inside Microsoft Dynamics 365 For Finance and Operations, it is necessary to grant the client access to this service. The following describes how to configure this access in Microsoft Azure Portal.

1 Install Model in Dynamics 365 for Finance and Operations

Use standard D365FO procedure when installing models.

If you are upgrading Mobile WMS from a version 3.4 or earlier, you need to remove the classes that are removed from version 3.5.

Once installed, you can find the Mobile WMS module here as shown on the image below.

2 Azure

2.1 Creating Microsoft Azure App Registration

Log into https://portal.azure.com using an administrator user associated with the D365FO environment you are maintaining.

After logging into https://portal.azure.com navigate to “Azure Active Directory” -> “App registrations”:

Click “New registration”:

To create a new application registration, you need to fill in the name field, make sure to select “public client (mobile and desctop)” and enter the URL to your environment.
This can be found from your LCS. Copy the link and you get this: https://YourLink-devaos.cloudax.dynamics.com/  

Under the Redirect URI choose “Public Client (mobile & desktop)” and enter your URL 

https://YourLink-devaos.cloudax.dynamics.com/ 

and then add OAUTH to the end of the string. 

Finally click “Register” at the buttom of the screen.  

2.2 Configuring the Application Registration

After creating the application registration, you then need to select the link “Redirect URI’s” marked in the red box below.  

Now add two additional URI’s: 

• /Soap/services
• /Soap/Services/MobService

See the next screenshot. Remember to insert your actual link.  

Also make sure that the types are “Public client (mobile & desktop)”. 

Then navigate to “API permissions” and click the “Add a permission” button. 

Depending on your rights you might have to have an admin person to “Grant consent” to your changes made to API permissions. 

Before you close the Azure portal make sure to make a copy of the application id: 

2.3 Configuration of Dynamics 365 for Operations

Log in to your D365FO environment and navigate to “Modules” -> “System administration” -> “Microsoft Entra ID applications”:

Click the “New” button:

The client id must be set to the value of the application id that was copied from the Azure portal. Then you give it a name and choose a user (the user will define what access rights the client has inside D365FO).

Then you click the “Save” button at the top.

This completes the setup needed for handheld clients to be able to access the Tasklet Factory WMS SOAP based service in your D365FO.

3 Device start.cfg configuration

In the START.CFG file the section 'Endpoints' specifies:

• endpoint id
• displayName
• type
• companyName
• address

But for Azure a few extra information’s is required. 

3.1 azureConfiguration authority

3.2 serviceName

3.3 clientId

3.4 returnUri

3.1 azureConfiguration authority => 

"https://login.microsoftonline.com/YourTennantId/oauth2/authorize"

Your tennant ID is found here: Azure active directory/Manage/App registrations (Preview)/ select correct name and click on it. Here you will find the tennant ID.

3.2 serviceName =>

"MobService"

3.3 clientId =>

Your client ID is found here: Azure active directory/Manage/App registrations/ select correct name and click on it. Here you will find the application ID.

3.4 returnUri => 

Azure active directory/Manage/App registrations/ click 'Redirect URIs'/select the URI with oauth at the end.

3.5 Update START.CFG

Now update the start.cfg with the 4 values.

<endpoints>
    <endpoint id="D365FO" displayName="D365FO" type="D365FO" protocol="classic" address="https://YourUriAddress">
    <azureConfiguration authority="https://login.microsoftonline.com/YourTennantId/oauth2/authorize" serviceName="MobService" clientId="YourApplicationId" returnUri="https://YourUriAddress/oauth"/>
    </endpoint>
</endpoints>

3.6 On-Premises

If you are running an on-prem solution then you need to make a slightly different setup. This is described here.

1) You need to create an application in your Active Directory Federation Services (ADFS). 

In PowerShell use the command "Add-AdfsClient" with redirect URI of your address. "https://<yourD365URI>/namespaces/AXSF/"

2) Grant permisson using "Grant-AdfsApplicationPermission -ClientRoleIdentifier "<taskletADFSclientId" -ServerRoleIdentifier "https://<yourD365URI>"

The endpoint is also slightly different.

  <endpoints>
    <endpoint id="MobileWMS" displayName="MobileWMS" type="D365FO" protocol="classic" companyName="" address="https://Your URI/namespaces/AXSF">
      <azureConfiguration authority="Your ADSF URI/adfs/oauth2/authorize" serviceName="MobService" clientId="" returnUri="Your URI/namespaces/AXSF"/>
    </endpoint>
  </endpoints>

4 Setup D365FO

This section describes the steps that shall be performed once per company.

4.1 One click Setup

Once the model is installed, your devices have full access to all menus.

This enables you to verify faster that Azure and Start.CFG is correctly setup. Once you have verified that access from the mobile device is working, it is recommended to setup user rights. Read more about that here: User Rights

Read more about configurations here: How to get started (AX/FO)

No main menu's after you login? (Applicable to Dynamics 365FO Version 3.14 or newer)

• verify that you have assigned the user to a user group
• you have assigned main menu's to that same user group
• Enforce a new application configuration version by navigating to "Mobile WMS/Setup/Pages" and select a random page. On this page you scroll down to menu items and move a menu item up or down. This will create a new version, and after you login again you will see all assigned main menu's. See image below marked in yellow the up/down buttons.

5 Solving Installation Problems

These problems are commonly seen.

6 User Roles in AX/FO

When using Mobile WMS the user must have below roles assigned.

7 Licenses

On the page: