Dynamics 365 Field Service

Currently, we can only remove the unmanaged layer of each component, that might be difficult when user unexpectedly created the unmanaged layer and find them to remove. We hope there will be a feature to remove all unmanaged customization in an environment

It should be possible to show only the schedule board from 17:00 (afternoon) until 8:00 (morning) for planners that specifically do the planning for night shifts. When I now try to configure this the system says it is not possible because the start date should be smaller than the end date.

So it should be possible to visualize the day in 2 parts, from 00:00 til 08:00 and the other from 17:00 until 24:00.

We have territories and subterritories. A territory could be like the province/county while the subterritory could be the city that is linked to the province/county. In the schedule board we need to have an overview of the planning on the territory level and when specifically scheduling on city level it should be possible to also filter on the subterritory level. This would mean that we have one filter "territory" and a second filter "subterritory" BUT the dropdown of the subterritory (second filter) should be limited to the subterritories linked to the territory (first filter). Otherwise, you can select a subterritory that is not even part of the territory. There is no way to make filter depending at the moment.

Currently, on both the desktop and mobile experience, the user is unable to jump to different pages.

They need to painstakingly click "Next" or "Previous" at a single time until they find the page they want.

May I suggest a dropdown control that lists all the Inspection pages, and selecting one of them navigates the user to that specific page. Additionally, add an indicator icon like a tick box next to the page in the list to show which pages have been completed and which ones haven't, so that users can track their progress more easily with larger inspections.

This feels like such a basic UX feature that is missing from Inspections, and it has caused a lot of frustration and time loss with the technicians who have been giving feedback regarding this functionality.

Thank you

When you have a 50 pager inspection template, if you want to go back to a question on page 2 while you are answering on page 30, you have to go through all the pages from 29 to 2. It would be better if we can jump in between pages.

This is already existing in the inspection template designer. There is already a drop-down of all the pages in the inspection and you can jump back and forth pages.

The dropdown filter selection for users (people picker?) is showing a lot of entries that are related to the solution and not actual users.

For example, the filter on Project Manager shows #PowerCards-S25-IL-Prod, #PowerQueryOnline, etc. This is across any table columns that are resource related.

We want to hide the Application users in the list of the lookup column under the Filter By in View page.

Integration of "appointments" is a nice feature within Universal resource scheduling since using OOB method, resources can self book their lunch breaks/urgent appointments etc. Hence lesser of day to day admin overhead for resource managers in larger organisations. Whilst the resource capacity is 1, the schedule assistant by default considers any appointment for the resource therefore doesn't propose being available during that time however if capacity>1, the schedule assistant ignores the appointment and still proposes the resource being available during its appointment time whereas the resource may have a self booked tea break/lunch etc. 

It would be great to have a Scheduling parameter setting for Schedule Assistant "Consider appointments for resource with capacity>1"(Yes/No) 

so the organisations could make use of this setting and allow staff to self manage there appointments regardless of the capacity of a resource.

RSO is a fantastic idea, however currently it only allows to schedule and optimise individual resources.

Majority of services companies have more than 1 resource booked to a job. we travel in 2 or 3 people and use trucks and the like.

We would like to see RSO being able to do this by utilising Resource Requirement Groups in the D365 Field service and project service.

thanks

Luka

The Schedule Assistant resets the 'Mode' that the suggested Resources and Times to List,

The Gantt view is often preferred by users as it is easier to use, which means very often as soon as the Schedule Assistant window opens, the user will click on the Gantt mode.

Suggestion is to:

1. Automatically save the last setting used by the user;
2. Ability to set the default for the environment.

Currently, an inspection question can be hidden or displayed based on a response of a prior question in that same inspection.

Would be nice if questions can also be hidden or displayed based on fields of the related work order (or further, such as the service account or customer asset). If the customer asset size = Large machine, additional fields are displayed to be filled in. If customer asset size = Small machine, those fields are not displayed.

This would eliminate the need to create and manage multiple inspection templates...

Imagine there is a one to one relationship between customer asset and work order. There are two factors on the customer asset for which you need additional fields displayed on the inspection (whereas the majority of other fields is exactly the same). For example: Customer Asset size has 3 options (large, medium, small) and Customer asset ownership has two options (Lessor, Lessee).

The amount of inspections templates required is:

• Inspection template 1: Large Customer Asset, owned by Lessor
• Inspection template 2: Large Customer Asset, owned by Lessee
• Inspection template 3: Medium Customer Asset, owned by Lessor
• Inspection template 4: Medium Customer Asset, owned by Lessee
• Inspection template 5: Small Customer Asset, owned by Lessor
• Inspection template 6: Small Customer Asset, owned by Lessee

Would be great if we can add the logic in the inspection template itself, rather than creating endless inspection templates to be managed separately!