Dynamics 365 Field Service

As per the following page column filtering in offline mode is not support. Please consider supporting this capability.

https://learn.microsoft.com/en-us/power-apps/mobile/offline-capabilities#limitations

-----------------

Grids

• Column filtering is disabled when an offline profile is set up even when there's network connectivity. The grid works with the local database and doesn't support custom filters.

-----------------

Currently a Team in Datavese can only be assigned with one mobile configuration profile. This is very limiting if you have a user who requires multiple offline profile-enabled apps to fulfil their daily duty.

It is not uncommon to have more than one app/form developed for users out on the field, having all apps inheriting just one profile could lead to many unused tables and add unnecessary load to the apps.

Please look into this issue.

It will be very helpful to see 4 lines e.g. for Servicetask from each record, because there are important Informations like

Resource / Taskname / Customer Asset Number and Customer Asset Short Description to pick immediately the rigth task.

Mobile View on Android:

 Only 3 Lines are shown

In Windows Mobile App:

 It works fine because of List view

The "Optimize Schedule" button on the Schedule Board Resource Cell lets dispatchers optimize the existing schedule of a chosen resource. Unlike RSO, Single Resource Optimization does not book new requirements but optimizes existing bookings. This feature is useful to fill gaps in the schedule that may arise due to Booking cancellations etc.

The idea is to extend this feature to add the ability to define a scope for the optimization run. For e.g. a scheduler might want to fill a schedule gap by booking Resource Requirements that fit a certain criteria. Similar to RSO, we will need to define a scope for Single Resource Optimization runs. If this idea were to be realized - when a user clicks on Optimize Schedule, in addition to optimizing the existing Bookings the system will book additional resource requirements fitting the criteria defined in the scope.

This will be a powerful feature for schedulers as it will enable them to build an optimized schedule for a chosen resource (a common business scenario) on a button click.

Currently, numeric keypad is displayed when phone number field is selected.

It is convenient if numeric keypad work when whole/decimal/floating fields are selected because it has large button on small display of mobile device. It should be enforced by Field Service Mobile App whatever mobile OS keybaord settings are.

There should be debugging tool for debugging JavaScript into the Field Service Mobile(Dynamic 365) APP.

Could you please consider to support landscape mode on iphone/Android in Dynamics365 Field Service mobile?

Now it seems that only portrait mode is supported.

When using the app on a tablet , we don't have the agenda view. We only have day, week or month view. But we don't see as much information in these views. Agenda view is also useful on a tablet.

Microsoft confirmed that the addcustomview() function is not supported in offline mode. Before release wave 2 2021, we used the function to create a custom View that would only show the Labour Codes assigned to a Bookable Resource via the Bookable Resource Category.

This view was then used when creating new Time Entries on a mobile device in Offline mode (using Field Service Mobile app) - when a Bookable Resource was creating a new Time Entry and they needed to select a different Labour Code to their Default Labour Code, they would only be shown the Labour Codes associated via the Resource Category Association.

As the addcustomview() function is no longer supported in Offline mode, it requires a User to search for a Labour Code via the Advanced Lookup; i.e. when a Labour Code is required that doesn't equal their Bookable Resource's Default Labour Code. This opens up the ability for the mobile User to select a Labour Code that is not associated with the Bookable Resource's Resource Category and thereby affecting Field Service's data integrity.

The suggestion is for the addcustomview() function to be fully supported in Offline mode.