Skip to main content

Asset Management Mobile App


Microsoft recently released a preview mobile app for Asset Management. The App gives 2 personas that you can use it for:


To install, go to AppSource to find the app Dynamics 365 Asset Management Mobile Application

Read the Onboarding doc page as there are prerequisites. Such as installing the Finance and Operations Virtual Entity solution.

The install is pretty easy to follow. Accept the terms and click Install.

A Canvas App will be installed and the virtual entities will be enabled in the background. Go and open the Canvas App.
You might get stuck on this screen at this initial preview release. It is a known issue and documented here. You just need to edit the canvas app and publish it.

Maintenance Requester

With the Maintenance Requester role, you will see the following screen. You can find your asset by searching or scanning. It looks like it will search on Asset Id and the Asset Type Id fields.

This is the create screen to enter a description and some notes.

Before you click, you can see the active work orders related to the asset.

Manage Work Orders

The functionality available (as per preview release in 24 March 2023) is to give feedback on a work order. 
The list shows work orders and jobs that are assigned to you only.
Search will work on the Work order id, Asset Id, Functional location Id.
Filtering is available by Today, This week and All.
Sorting is available by Work order id, Service level and Start date.

A work order has to be scheduled to you for it to appear. I had to dig into the canvas app code to see the filtering applied. Because initially I couldn't see anything.

Overall, it looks really good. I will keep exploring. 

Popular posts from this blog

AX - How to use Map and MapEnumerator

Similar to Set class, Map class allows you to associate one value (the key) with another value. Both the key and value can be any valid X++ type, including objects. The types of the key and the value are specified in the declaration of the map. The way in which maps are implemented means that access to the values is very fast. Below is a sample code that sets and retrieves values from a map. static void checkItemNameAliasDuplicate(Args _args) { inventTable inventTable; Map map; MapEnumerator mapEnumerator; NameAlias nameAlias; int counter = 0; ; map = new Map(Types::String, Types::Integer); //store into map while select inventTable { nameAlias = inventTable.NameAlias; if (!map.exists(nameAlias)) { map.insert(nameAlias, 1); } else { map.insert(nameAlias, map.lookup(nameAlias) + 1); } } //retrieve fro

AX - How to use Set and SetEnumerator

The Set class is used for the storage and retrieval of data from a collection in which the values of the elements contained are unique and serve as the key values according to which the data is automatically ordered. You can create a set of primitive data types or complex data types such as a Class, Record or Container. Below is sample of a set of records. static void _Set(Args _args) {     CustTable       custTable;     Set             set = new Set(Types::Record);     SetEnumerator   setEnumerator;     ;     while select custTable     {         if (custTable && !         {             set.add(custTable);         }     }     if (!set.empty())     {         setEnumerator = set.getEnumerator();         setEnumerator.reset();         while (setEnumerator.moveNext())         {             custTable = setEnumerator.current();             info(strfmt("Customer: %1",custTable.AccountNum));         }     } } Common mistake when creating a set of recIds

Import document handling (attachment) files #MSDyn365FO

Out of the box you have limited data entities for migrating attachments. If you search what is already in the AOT, you will see a few various examples. I suggest you look at the LedgerJournalAttachmentsEntity as it is the simplest and cleans to copy from. I wont go into detail but I will give a quick run down of what it looks like. Use the DocuRefEntity as your main datasource. It does most of the work for you. Set your table you want to import for as the child datasource Add the Key You will need to add the postLoad method. There is minor code to update the virtual field FileContents. Below is an export I did for the general journal attachments. The import zip structure should be the same way. It will create the usual artifacts such as the excel, manifest and package header xml files. You will see a Resources folder under that. If you drill down to the resources you will see the attachments. This is an export and it used the document GUID for uniqueness. The other thing is the extensi