This is an update to my previous post - https://daxdilip.blogspot.com.au/2017/03/dynamics-365-for-operations-tip-mobile.html, where I shared a workaround on how to view the out of box mobile workspaces from System Administration > Parameters form and publish them.
This workaround is no longer needed as in this post, i will explain the steps on how to achieve the same using standard process:
As you are aware, that wiki is being deprecated, and now Microsoft is moving to a new docs site for D365FO help, so keep an eye on Dynamics 365 for Operations Mobile Workspaces as this is the page where Microsoft will publish their upcoming mobile workspaces
At the moment, we have the following workspaces for mobile
- Expense Management Mobile Workspace
- Project Time Entry Mobile Workspace
- Cost Controlling Mobile Workspace
- Mobile Invoice Approvals
- Vendor Collaborations Mobile Workspace
Most of the above workspaces are linked to a Hotfix which can be downloaded from LCS
Previously on wiki, We had Inventory on hand and sales order workspaces, but looks like they are not ported to the new Dynamics docs site.
In this post, I will walk through an example of setting up mobile workspaces for sales order and inventory on hand.
Go to LCS > Project > Issue Search and search for the below KB or just click on this link
Download KB 4013633 (an X++ update or metadata hotfix). This contains four mobile workspaces for supply chain management.
Once you download the hotfix, extract it to your VM where you want to install the hotfix. Since this is a metadata hotfix, this needs to be treated bit differently, as it can't be installed from Asset Library.
Log in to your VM and then use the SCDPBundleInstall command
SCDPBundleInstall.exe -install -packagepath=c:\temp\HotfixPackageBundle.axscdppkg -metadatastorepath= J:\AOSService\PackagesLocalDirectory
Tip - Note in some of the later VM's you will find the SCDPBundleInstall in the Bin directory inside PackagesLocalDirectory i.e. J:\AOSService\PackagesLocalDirectory\Bin
Once the bundle installation is successful, next step is to go to Visual Studio and create a deployable package as shown below:
Once the deployable package is created, go to Asset Library and add the deployable package in software deployable package Asset type
Now, you should be able to go to your environment where you want to apply the deployable package and then click on Apply Updates from maintain environment and select the deployable package and start deploying.
The environment will go into Servicing state and no one will be able to use the environment at this point. This may take 1 to 2 hours to get deployed.
Once the package is deployed, you can now go to System Administration > Parameters > Mobile parameters and pubilsh the default mobile workspaces and start using them