Skip to main content

Dynamics 365 for Operations mobile platform–Part 2

In the previous post, I showed my first experience with downloading the application. In this post, I will give some examples of setting it up.

First enter the url with &mode=mobile

https://myfakeaos.cloudax.dynamics.com/?cmp=usmf&mi=DefaultDashboard&mode=mobile

On the top right menu you will see Mobile app.

image

This will slide through the configurations pane.

image

Click on Add and create your first workspace.

image

 

image

I navigated to the form I want to record. I went into the On-hand inventory form.

image

Clicked on Select fields button and these orange + signs came up. Select the fields you want to display on the mobile device.

image

Click on the Done buttons. Then click on Publish workspace.

image

 

image

Refresh the mobile app.

image

image

 

image

This would have been really cool if it worked but I had a issue. It only displayed 1 item in the list.

The onhand form is very complicated and has a lot of dynamic features. Hiding and showing inventory dimension. So, I would recommend creating your own simple inventory on hand form which doesn’t have the complications of the standard form.

image

I did the exact same thing for the Released products and it worked fine.

image

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.in(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