Author: 
Mobile Platform for Dynamics 365 for Finance and Operations

Mobile Platform for Dynamics 365 for Finance and Operations

Mobile compatibility for Dynamics 365 is a game changer in the world of ERP in an age where mobiles are becoming as powerful as personal computers and allowing many tasks to be performed faster and better than before. It provides easy access to many of ERP modules and features in Dynamics 365 for Finance and Operations. It also enables developers to create simplified forms in visual studio and then design mobile pages to expose functionality.

Accessing Dynamics AX modules on mobile enables the organization to perform its business-related tasks on mobile devices. The user simply signs in and immediately begins to run business processes, boosting productivity.
 

Key Benefits

  • Reuse business logic and modeling
  • Create your workspace
  • Easy to develop
  • Mobile Workspaces
  • Instant access to information
  • Full offline support
  • Modify according to your need
  • Enrich mobile experience

Architecture and design

Dynamics 365 for Finance and Operation mobile app communicates with AOS to get metadata. The mobile app caches the data so even when the connection with the server is lost, it will keep working offline.

One you launch the mobile application; a new user session will be created. Application will communicate with AOS to get metadata for workspaces. Each time a form is open, a new user session will be created. When an operation is performed, the session will be created and the operation will be submitted to the server. The server will respond with the success or failure of the operation.

Getting started with Mobile App

Get the sample workspace

Creating your own workspace

Using the mobile app designer

Creating a list view

Things to make sure:

  • Identify or create a form in Dynamics 365 for Operations that contains a grid for the entity.
  • Make sure that the grid is bound to the table that represents the entity.
  • Make sure that the form has a menu item that is root-navigable.
  • Make sure that the form can be opened directly via a URL that includes the menu item parameter.

Make sure that the filter pane enables the grid to be filtered based on the desired fields.

Creating a detail view

Things to make sure:

  • Identify or create a form in Dynamics 365 for Operations that contains the details view for this entity.
  • Make sure that the Master Root Data Source on the form is bound to the table that represents the entity.
  • Make sure that the form has a menu item that is root-navigable.
  • Make sure that the form can be opened directly via a URL that includes the menu item parameter.

Creating list-to-details navigation

Things to make sure:

  • Make sure that you have created both a list view page and a details view page for the entity by using the designer.
  • Make sure that the entity for the list view is the same as the entity for the details view.
    In other words, the table that is bound to the grid on the form that is used for the list view must be the same table that is the Master Root Data Source on the form that is used for the details view.
  • Make sure that the form that is used for the details view can be filtered on a unique key field by using the filter pane.

Create Actions:

Create new button:

Things to make sure:

Make sure that the form that is used for the list view page includes a New button that can be used to add new records to the list.

Create Delete button:

Things to make sure:

Make sure that the form that is used for the details view page includes a Delete button that can be used to delete the visible record.

Create Edit button:

Things to make sure:

  • Make sure that the form that is used for the details view page includes an Edit button that can be used to edit the visible record.
  • Make sure that the form that is used for the details view page lets users open a specific record by applying filters in the filter pane.

Enabling a field value to be set via a rich lookup

Things to make sure:

  • Make sure that the field on which you want to add the lookup has an entity behind it.

Refreshing the app after making changes

From Design Requirements

  1. Each form must have an associated Display Menu Item.
  2. Each form must be directly accessible via its Display Menu Item.
  3. Each form that shows data must have one Master Root Data Source.
  4. Each form must work with the data source filters.

References

https://docs.microsoft.com/en-us/dynamics365/unified-operations/dev-itpro/mobile-apps/platform/mobile-platform-home-page

Mobile workspaces

https://docs.microsoft.com/en-us/dynamics365/unified-operations/dev-itpr...

Categories: 
Fahad Naeem's picture
Associate software engineer at Systems limited based out of Lahore. Boasts a demonstrated record of working in the information technology and services industry.

Disclaimer: The views expressed here are solely those of the author in his private capacity and do not in any way represent the views of Systems Limited, or any other entity related to Systems Limited.

Add new comment