Skip to main content

PowerApp with Dynamics 365 for Operations #D365O

Recently, I spent I bit of time on PowerApps. Below is a walk through of my findings.

Go to https://powerapps.microsoft.com and log in. This will take you through to the PowerApps dashboard. Here you can define your connection. This step requires that you authenticate to your D365O. Based on your email it will list all the D365O you have on your tenant.

image

You can then create a new Application now. Click on Get started under the Create an app menu.

image

First thing it comes up with is the connection. Select D365O and the Odata services will be listed. I chose to select the InventorySitesOnHand.

image

Wizard will default 3 pages.

  • List
  • Details
  • Edit

You can change the layout and the fields easily. Just click on the page to change the layout. Click on the field to select or change the field.

image

You can save your application.

image

If you run it, it will give you a preview.

image

Download the App on your mobile

Now this below is from my personal android phone. PowerApps will list all the apps you have published.

SNAGHTMLb57a6b7

This is the final result

SNAGHTMLb58bba2

I haven’t done formatting but this is how the details page looks like.

SNAGHTMLb5ab1b5

It is an online app. If you go offline and try to access the app. Then you will get an error.

SNAGHTMLb67e49d

Lastly, you can pin the app that was published.

SNAGHTML651cd1a

When you pin it, it will go on your home screen.

SNAGHTML652af7b

There are a couple of posts which I found to be useful

https://dynamics3654operations.wordpress.com/2016/11/13/powerapps-for-dynamics-365-for-operations-part-1/

https://dynamics3654operations.wordpress.com/2016/11/24/inventoryonhand-a-first-powerapp-for-dynamics-365-for-operations-part-2/

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