Bérangère DUVAL Consultante

Hello, it is necessary to make it possible to establish typologies or titles for quick reservation notemsdyn_bookableresourcebookingquicknotes

This would address the needs expressed by many clients to categorize the information conveyed by resources during their interventions with clients.

Also, most clients request that the "msdyn_bookableresourcebookingquicknote" be integrated into the PDF report signed by the client. This way, the notes could be neatly listed along with their typology. For example: work completed - work needed before the next intervention - information to be communicated to the sales team, etc.

When users needs to change schedule board settings, they open settings from schedule board. Parameters window open, when user change a parameter, window is automatically close. That mean user had to reopen parameters for each parameters they need to change.

While the current design of Dynamics 365 does not support creating alerts for custom score satisfaction metrics, it is crucial for Microsoft to address this need and develop the functionality. This limitation represents a significant gap in the product's capabilities. It would be very beneficial to be able to set up alerts for all types of metrics, allowing clients to efficiently process customer feedback.

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.

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.