Dynamics 365 Field Service

Deleting a time-off request record should also remove the corresponding time-off entry from the schedule board or resource's calendar. This functionality will greatly enhance user convenience and efficiency. 

Our customer needs the feature back to synchronize the bookable ressource bookings to outlook calendar. Is it possible to enable again this feature? Why is it deprectaed? It looks for me like a really nice feature for the field service agents.

We want to use booking rules on the Quick Create form of the Bookable Resource Booking.

Apparently this is not supported at the moment.

It would be really fantastic if the activity timeline had more options for sorting by the date of the associated activity object. For example, emails often appear our of chronological order if they have not been tracked in order. It would be great if for example the email sent/received date could be used for timeline sorting.

Thanks

John

When our customers using Resco to sync their video from the mobile app to Dynamics 365, if the sync time exceeds 3 minutes, they will receive a timeout error message. Please extend the timeout more to let our customers upload their large files into Dynamics.

Obtaining the resource booked hours on a given day is currently not possible through the OData API. The API doesn't return the breakdown of hours booked for a resource. Example - one resource booked 9:00 AM - 1:00 PM as working hours, then next 1 hour as break followed by 4 hours of work from 2:00 PM - 6:00 PM.

The Odata API doesn't return the time breakdown in the response for given calendar of a resource. Adding this support will help in many reporting application eventually helping with resource planning and understand the utilization of the resource in the organization.

Even completed resource requirement can be still scheduled using new schedule board which effected our business very badly.

so make a restriction on the resource requirement to prevent scheduling completed resource requirements again.

Customers often have multiple time windows for their availability, which can vary across different days of the week. In Field Service - RSO, the scheduling engine currently only considers time constraints defined in the Promise Window (Promised Start Time and Promised End Time). This approach is insufficient when a customer location has specific constraints, such as being closed during lunch hours or closing earlier on Saturdays and Sundays.

By default, the Account table includes a column called 'Work Hours Template', which gets copied to the Resource Requirement when a Work Order is created.

I propose an enhancement to the scheduling logic to either:

1. Leverage the Work Hours Template as a time-based constraint directly on the Resource Requirement.
2. Provide a solution to capture and apply multiple time windows (e.g., closed hours or variable hours) in the scheduling process to ensure accurate and efficient scheduling

The auto save feature is not available for any apps except model-driven app. This option should be available for every platform because of its convenience and user-friendly features. Please consider enabling the auto save feature for Dynamics mobile apps.

The current method of managing work hours for resources in Field Service requires setting individual calendar rules for each day or defining a fixed end date for recurring patterns. While functional, this approach can lead to inefficiencies when handling large datasets, as seen in scenarios with thousands of calendar rules.

A customer managing an interpreter pool resource encountered significant performance degradation caused by over 7,000 calendar rules. This not only led to timeouts when modifying child resources but also required manual intervention to delete historical data spanning thousands of years.

To resolve the issue, the customer implemented a 24-month limit on work hours and committed to periodic updates. However, they identified an opportunity to enhance the system’s functionality by automating the extension of recurring patterns.

Introduce a feature that allows administrators to:

1. Set a recurring work hour template for resources without requiring an explicit end date.
2. Automatically extend the recurring pattern by a user-defined interval (e.g., one month) once the current pattern is a specified duration from expiration (e.g., 12 months out).

Suggested Implementation Details:

• Introduce a configuration option in the work hours setup to enable auto-extension.
• Allow administrators to specify the extension interval (e.g., monthly, quarterly, annually).
• Provide notifications or logs to inform users when the system extends work hours.

This would prevent the accumulation of excessive calendar rules, improving system responsiveness when modifying resources and reduces the need for manual updates to work hour templates.