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.