This section describes how to retrieve and deploy the Dynaway Mobile for Asset Management (AM) solution in D365FO, using Microsoft Lifecycle Services (LCS).
This installation procedure covers deployment into cloud-hosted environments for demo, development, and user acceptance testing purposes. It does not cover installation into a production environment as these environments are managed and operated by Microsoft®.
In order to complete installation by following this procedure, you must be familiar with Microsoft Lifecycle Services (LCS) and administration of Microsoft Dynamics® 365 for Finance and Operations environments. For topics not covered in this installation procedure, refer to Microsoft® deployment guidelines on Microsoft Docs website.
If you want to install Dynaway Mobile for EAM, first you must acquire a license file. In order to acquire a Dynaway Mobile license file for EAM in Dynamics 365 for Finance and Operations, send an email to email@example.com and provide the following version information:
Find this information in Dynamics 365 for Finance and Operations by selecting Help & Support (the question mark icon in the upper-right corner of the application) > About.
If you update your Dynaway Mobile solution from an older version to a newer version, the license file may also need to be updated due to certificate updates.
The procedure described in this chapter can be omitted if the Dynaway Mobile solution is already available in your LCS project.
The Dynaway Mobile solution is published and distributed using the Asset Library in the Microsoft LCS project. In order for the Dynaway Mobile solution package to become available, it must be imported into the Asset Library by a representative of Dynaway. This means that Dynaway needs temporary access to your LCS project.
Follow the step-by-step instructions in the test case below to grant access to a Dynaway representative in your LCS project.
Recommended for security purposes: When the Dynaway Mobile solution has been imported to your LCS project, the added Dynaway users can be removed again. Future versions will automatically be available when they are published.
In your new project > More tools section > select Project users.
Select the plus sign (+) to add a new user. Leave the User lookup field blank.
In the Email field, enter the following email to request access from Dynaway: firstname.lastname@example.org
In the Project role field, select "Project team member". See screenshot below.
On the Project user management screen, you've been added with status "Pending". The first time you log on to LCS, the status will be updated to "Accepted". See screenshot below.
If you want to invite other users to your project, repeat steps 2-5.
Notify Dynaway Support that you require the Dynaway Mobile solution package by sending an email to email@example.com.
Please specify your customer name and the name of your LCS project.
Dynaway Support will then add the Dynaway Mobile solution to your LCS Project Asset Library. The reply email is from EG Service Desk.
The user can invite Dynaway to an LCS project, for the purpose of installing Dynaway Mobile in D365FO.
When you have completed the procedure described in the article Invite Dynaway to your LCS project, the Dynaway Mobile solution is available in the Asset Library of your LCS project. To see the Dynaway Mobile solution package contents, go to the Asset Library.
Refer to the step-by-step instructions in the test case below to get an updated version of Dynaway Mobile for Asset Management in LCS.
Refer to the Release overview article for an overview of compatibility between major Dynaway Mobile versions and Dynamics 365 for Finance and Operations Application Updates.
Refer to our Dynaway Mobile Release Notes for further details on version content and compatibility with Microsoft updates to Dynamics 365 for Finance and Operations.
Go to your LCS Project Asset Library and select Solution package.
Select the Dynaway Mobile for Asset Management solution.
Select Versions to view the list of available versions.
Select the most current version.
Select Get version.
You can get an updated version of Dynaway Mobile for Asset Management in LCS.
The latest version may contain builds for multiple Application Updates from Microsoft.
This article describes how to deploy Dynaway Mobile into an existing cloud-hosted environment using LCS.
The Dynaway Mobile module is deployed into existing environments using the environment management section of LCS. When the Dynaway Mobile solution has been imported into the LCS project as described in the article Get mobile solution in LCS, deployable packages will appear in the list of applicable updates.
Note: Before deployment, ensure that the active version of Dynaway Mobile in LCS is compatible with the Application Update version of Dynamics 365 for Finance and Operations.
Refer to the test case below for step-by-step instructions on how to deploy Dynaway Mobile to an existing cloud-hosted environment.
When you have completed deployment of the Dynaway mobile solution, next step is to import the license file, which is described in the next article.
Go to the existing environment in LCS.
Select Apply updates.
Select Dynaway Asset Management Mobile [version number] in the list.
Select Apply and wait until the process completes. This may take several hours.
You are able to deploy the Dynaway mobile solution into a cloud-hosted environment by using LCS.
This section describes how to import the Dynaway Mobile for Asset Management license file into Dynamics 365 for Finance and Operations using a deployable package.
Prerequisite: You already have a license file (.txt) from Dynaway, as described in the Acquire license file section.
Dynaway Mobile uses ISV licensing as described on Microsoft Docs: Create a package and generate a customer-specific license.
Microsoft provides a tailored template package for importing ISV licenses. In order for it to work, it must be populated with your own specific Dynaway Mobile license file.
Follow the step-by-step instructions described in the three test cases below to create a deployable package, then upload it and import it.
Make a remote desktop connection to an environment running the same version as your target environment.
Navigate to the CustomDeployablePackage directory under the AOSService folder <PackagesFolder>\bin\CustomDeployablePackage\ImportISVLicense.zip.
Make a copy of the template package "ImportISVLicense.zip" and rename the copy.
Example: Rename the file to "DynawayMobile_ImportISVLicense.zip".
Open the zip package file.
In the zip package file, navigate to the sub folder "\AosService\Scripts\License". Copy the license file you received from Dynaway to this folder.
Delete the placeholder file "place your license file here.txt".
Close the zip-file.
You have created a deployable license import package file.
Open the Asset library of the target project in LCS.
Navigate to Software deployable package.
Select the "plus" button.
Add the deployable license import package file.
Enter a name for the deployable package.
In LCS, navigate to the target environment.
Select Maintain and Apply updates.
In the list, select the newly added license package.
Select Apply and wait for the process to be completed.
Select Sign-off to complete the process.
Open Dynamics 365 for Finance and Operations to verify the Dynaway mobile module is available in the main menu of Dynamics 365 for Finance and Operations.
You have imported the license package file into LCS.
The Dynaway mobile module is available in the D365FO main menu.
This article describes the recommended initial setup of the license configuration values for new Dynaway Mobile deployments. Depending on your version of Dynaway Mobile, the recommended setup may already be the default setup.
In order to change the license configuration, the Dynamics 365 for Finance and Operations environment must be in maintenance mode. Refer to Microsoft documentation for details on how to enable Maintenance mode.
The process of updating Dynaway Mobile is similar to the processes used for installing Dynaway Mobile into an existing environment, as described in other articles:
After the update process, carry out the follwing tasks: