Skip to main content

Inventory on-hand mobile workspace for Microsoft Dynamics 365 for Operations app

Over the last couple of months I posted about the Dynamics 365 for Operations mobile platform.

Part 1 – Logging in

Part 2 – Basic configuration

Part 3 – Advanced configuration

Part 4 – Export/Import

I intentionally say platform and not app. This is because it is somewhat a generic in nature. You can record a series of forms and actions to use as an app. The App behaves similar to the full browser application by focusing on workspace concept. You click on a workspace and drill through to menu items.

Search for a KB 3215650 that will allow you to deploy 4 recorded apps done by Microsoft. This hotfix includes the workspaces for Supply Chain Management listed below. More information on the wiki links below.

Focusing on the Inventory on-hand workspace. Below are some screenshots.

You get 4 workspaces that Microsoft provided. Drill into the Inventory workspace and you get one option

SNAGHTMLc74505fSNAGHTMLc74d2af

  You get the item list to search. The when you drill through you have basic information with some links. Notice the different action available to see availability on.

SNAGHTMLc764876SNAGHTMLc769b1a

I had some labels missing here. Next time I will try to dive in deeper to find out more.

SNAGHTMLc780fc9

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