Dynamics 365 Field Service

There can be multiple types of breaks in a schedule for instance long break and short break. Currently, segregation of breaks or any other event does not exist in scheduling feature. For users, who have clear distinction between different types of breaks or any other working and/or non-working event, there is no support to add description as well. Making event types configurable or adding description field for all events can improve usability and experience.

💡 Description:

Currently, the decimal precision of Number-type questions in Inspection Templates is affected by the "Pricing decimal precision" setting in environment behavior settings (PPAC > Environment > Settings > Behaviour).

This behavior is confusing and unintuitive for the following reasons:

• Number questions are typically used for general numeric inputs (e.g., temperature, quantities, scores), which are not related to pricing or currency.
• The "Pricing decimal precision" setting is intended for controlling decimal places in currency fields, as clearly documented.
• Customers are reluctant to change this setting, as it also affects existing Dataverse currency fields across the environment.
• This hidden dependency can lead to inconsistent behavior, especially when using different base languages (e.g., English environments default to 2, Japanese environments default to 0).

🎯 Proposed Improvement:

Please consider decoupling the precision of Number-type questions in Inspection Templates from the "Pricing decimal precision" setting.

Instead, allow these questions to:

• Have their own explicit precision setting, or
• Default to a reasonable number of decimal places (e.g., 2), independent of pricing-related configurations.

🔍 Business Impact:

This behavior is currently blocking customers from using decimal values in Number-type questions without affecting global currency formatting.

It creates avoidable confusion and increases the risk of unintended side effects when adjusting a setting that is supposed to affect only currency fields.

For work schedules that span two consecutive days, a break slot may fall across midnight. For example, if a shift starts at 8:00 PM and ends at 5:00 AM, a break could be scheduled from 11:45 PM to 12:15 AM. In such cases, msdyn_SaveCalendar will be called twice — once for the preceding day and once for the next day. However, for the next day, handling a break slot that starts at 12:00 AM (e.g., 12:00 AM to 12:15 AM) is currently not supported. Allowing break to appear at the start of the day to handle such scenario can help in scheduling overnight shifts.

Displaying both Estimated Hours and Actual Hours within a single time entry to better track time entries

On the Sub-grids within Field Service forms, the search or "Quick Find" states "Apply Begins with filter on these columns: xxx"

This is NOT configurable by system admins and means users must be coached to use wildcard (*) to override this type of filtered search to be Contains.

I suggest that Microsoft allow system admins to be able to configure their preference of the filter type within Quick finds across the various tables.

This will give a much improved user experience.

I would like to highlight a limitation of the Booking Status component in Field Service forms. As mentioned by the Microsoft support team, this component is designed for a small number of statuses. When there are more than about ten booking statuses, the component behaves unpredictably, causing the list to move up and down without user action.

Despite this limitation, customers appreciate the organizational ease provided by booking statuses. These are simple to use and configure, allowing Field Service to adapt to various business contexts.

It would be helpful if Microsoft could enhance this component to handle a larger number of booking statuses without performance or usability issues.

Show Calendar entity audit on D365 CRM or modify CanModifyAuditSettings to true for Calendar entity

We have identified a significant gap in the functionality of Microsoft Field Service that we believe, if addressed, would greatly enhance user experience and efficiency. Currently, when creating an email from a work order, the system does not automatically populate the "To' field.

This feature is available in other tables such as incidents and opportunities, but not in work orders.

Upon contacting Microsoft Support, we were provided with a script to manually add to our forms, as this functionality is not available out-of-the-box. While this workaround is appreciated, it is not an ideal solution for all users.

It would be appreciate to have a standard feature that automatically populates the email recipient field with the contact specified in the "Reported By" field, or with the service account if the contact is empty. This enhancement would streamline the process, reduce manual entry errors, and save valuable time for Field Service users.