Check the other articles of this series

Continuing the previous post,

In this post let us try configuring the Dashboard for mobile.

We have created a custom dashboard having the test entity and have kept the “Enable for mobile” option as unchecked

Now let us add this dashboard in our model-driven app and update the sitemap.

Publish the changes and open the app in the mobile app.

The Dashboard is available within the app, even though the option “Enable for mobile” was unchecked.

Here we need to make sure the user has the Dashboard is accessible for the security roles(s).

Some of the system dashboards will have “Enable for mobile” property already checked and greyed out.

As we already saw, this property doesn’t have any effect in the case of the model-driven app, so to make these dashboards available for the end-user, we just need to add them to the App.

The dashboard within the mobile app.

Now let us try adding an Interactive Dashboard to the app.

The Interactive Dashboard shows up within the tablet app for windows, with a horizontal scroll bar.

And the same inside the phone app for android, displayed vertically considering the screen size.

Now let us check the behavior with the personal dashboard.

Say e.g. user1 (system admin) has created the following personal dashboard named personal dashboard.

The same is displayed for the user within the mobile app.

As expected, it is not available to another user, considering it is a personal dashboard.

Let us share the dashboard and check.

The personal dashboard will be available to the user to who it has been shared.

It seems like with earlier version it was not possible

https://community.dynamics.com/crm/f/microsoft-dynamics-crm-forum/208534/crm-dashboard—viewing-shared-dashboard-on-mobile

Thus, we covered how to add the dashboards to the app and the way they render within the mobile app.

We have also shared our feedback on some of our findings on Microsoft docs

Hope it helps..

Check the other articles of this series

Continuing the previous post,

Now let us see how do we enable a specific entity for mobile.

To begin with, let us first create a custom entity named Test. For now, let us leave the Enable for mobile option unchecked.

[Update – Enable for mobile has been renamed to Enable for Unified client]

We have created a new model-driven app and added that entity in the sitemap.

Let us publish the changes and try accessing the app from Dynamics 365 mobile app.

Even without checking “Enable for mobile” option, the Entity is available as it is part of Model-Driven App and we are accessing it using System Administrator that has rights on both the app as well the custom entity.

Now let us check that option along with read-only option on the custom entity and publish the changes

This setting makes the entity as read-only for the user (even System Administrator)

Now let us update the site map, add the same entity inside sub-area, also create a new group and new area and add the same entity.

Let us save and publish the changes and see how it gets rendered inside the mobile app.

Below how it displays the navigation, exactly as specified in the Sitemap, inside Dynamics 365 for the Tablet app and Phone app.

Microsoft Documentations says

https://docs.microsoft.com/en-us/dynamics365/mobile-app/set-up-dynamics-365-for-phones-and-dynamics-365-for-tablets#navigation-bar

which it seems it doesn’t apply with the Model-Driven app anymore.

Hope it helps..