Dynamics 365 Field Service

Dear MS team,

When you filter your data (esp. work orders and customer assets), it should be easily possible to switch to a map view with one click and vise cersa. On the map spots are shown based on the geo-coordinates which are deposited in the records. This function is a standard function e.g. in the resco mobile app and should be also a matter of course in a tool like the field service mobile app from MS.

BR,

Willi

Dear MS Team,

I very often get complaints, that the performance of the field service mobile app is too bad. We just work online because the offline profile is not usable (download takes too long, personal views are not available, etc.). What in my eyes really impairs the performance in the online mode are the workflows/cloudflows which are working in the background (e.g. during saving a record). By having them offline available (in win app and phone app), I think the app in total would work much faster.

BR,

Willi

Currently we can not modify the task from the schedule board once it is assigned . please allow us to do the modification from the schedule board . Once record is used in the schedule board . Please allow us to do that

2.Please allow us to drag and drop multiple activities at once .Currently we can drag and drop only one activity at once in the schedule board

Hi Team,

Please check the idea from our valuable customer below:

Problem Statement

Customers need the ability to view configured booking tooltip fields when hovering over bookings in Daily/Weekly/Monthly views. Today, the “Booking tooltips view” setting is documented and implemented to affect Hourly view only. In interday views, tooltips are either limited to a fixed template or behave inconsistently depending on the schedule board tab implementation (for example, legacy/older behavior vs the New Schedule Board). This creates operational disruption for customers who relied on tooltip-driven workflows for years and now see the behavior removed or inconsistent after newer schedule board updates aligned to current design.

Current Behavior (As‑Is)

1) “Booking tooltips view” impacts Hourly view only (by design / per documentation).

2) In Daily/Weekly/Monthly (interday) views, tooltips may:

  - Not reflect the configured tooltip view, or

  - Show only a minimal fixed set of fields, or

  - Behave inconsistently across schedule board tabs/environments depending on underlying implementation.

Business Impact (Why this matters)

Dispatchers/schedulers depend on hover tooltips to quickly validate booking/work order details without opening each record. When interday tooltips don’t show configured data, schedulers must manually open records, reducing productivity and delaying scheduling decisions. This gap contributes to customer dissatisfaction when a previously relied-on workflow no longer behaves consistently.

Requested Enhancement (To‑Be)

Provide a supported, configurable, and consistent way to display Booking Tooltip information in Interday views (Daily/Weekly/Monthly) on the New Schedule Board, while ensuring tooltip content remains accurate and safe when bookings are aggregated.

Goals

1) Allow customers to see meaningful booking details on hover in Daily/Weekly/Monthly views without opening each record.

2) Ensure tooltip content is accurate, especially when the hover target represents multiple underlying bookings (aggregates).

3) Provide a supported configuration so customers are not relying on legacy/unsupported behavior.

Success Metrics 

- Reduced need to open booking/work order forms during dispatching (fewer clicks and record opens).

- Improved hover latency and stability (no crashes, consistent tooltip rendering).

- Reduced support escalations related to tooltip inconsistency across schedule board tabs.

- Higher customer satisfaction with interday scheduling workflows.

Before the 2026 wave 1, there was the possibility to filter columns from related entities in the Requirement Pane. Now you can filter only the columns from the Resource Requirement table which severely impacts the resource scheduling time.

MS Support said that this behavior has been reviewed internally and has been identified as a known product limitation within Dynamics 365 Field Service, but in the meantime I confirmed that on older versions of FS the filtering is working fine.

Current behavior:

When a Functional record is set up, and Bing map integration is set up, each record will have to manually be opened and 'Geo code' command has to be clicked to fetch the longitude and latitude coordinates of the address.

Business Impact:

For organization with multiple locations, this requires users to have to manually go through the process to retrieve and save the coordinates to the records.

Enhancement request:

Since the system already has a function to fetch the coordinates, please consider adding an asynchronous trigger to fetch these coordinates, for example: on address field being updated.

Benefit:

This will let the data be pulled automatically, and reduce manual labor. Additionally, coordinates are often used for geo fencing service areas, so this will allow a smoother workflow for service providers.

Microsoft has delivered a documented improvement of at least 25% faster form load times on Android devices as part of the Dynamics 365 Field Service release wave, achieved through client/runtime optimizations and enabled automatically for users.

However, similar quantified performance improvements are not currently documented or available for iOS devices (iPhone/iPad), even though a significant segment of Field Service technicians and supervisors rely on Apple devices in real‑world deployments.

This creates an experience gap across mobile platforms where:

• Android users benefit from measurable form load improvements
• iOS users continue to face relatively slower form rendering, especially for form‑heavy scenarios and offline‑first usage (In couple if implementation of Field Service Mobile app our majority users are iPad, iPhone )

Business Impact

In enterprise Field Service implementations:

• iPads are often used by supervisors and lead technicians
• iPhones are widely used for quick work order updates, inspections, and status changes

Slower form load times on iOS can directly impact:

• Technician productivity and time‑to‑first‑action
• Adoption of complex or customized forms
• User satisfaction in offline or low‑connectivity environments
• Consistency of mobile experience across mixed device fleets (Android + iOS)

Requested Enhancement

Introduce equivalent client/runtime performance optimizations for iOS (iPhone and iPad) in the Dynamics 365 Field Service mobile app that:

• Improve form load times by a measurable and publishable percentage, similar to Android
• Work automatically without additional configuration or retraining
• Fully respect existing form customizations and offline profiles
• Allow customers to track improvements using existing UCI or Application Insights telemetry

Expected Value

• Consistent mobile performance across Android and iOS
• Improved technician productivity on Apple devices
• Faster adoption of advanced Field Service scenarios
• Stronger confidence for enterprises standardizing on iOS hardware

With Microsoft already demonstrating that form‑load optimizations are achievable on Android, extending the same engineering focus to iOS would close a key gap and reinforce Field Service Mobile as a platform‑agnostic, performance‑first solution for frontline workers.

Following a recent Dynamics 365 service update, the default behaviour of the requirement search filter in the Schedule Board requirement panel has changed from “Contains” to “Starts With.”

Previously, the default “Contains” filter allowed users to quickly locate requirements using partial or flexible search terms, making the search process more efficient and user-friendly. With the new update, users are now required to manually change the filter from “Starts With” to “Contains” each time before entering their search criteria.

This additional step impacts productivity and usability, especially for users who frequently rely on the requirement panel for searching records.

We recommend restoring the default filter behaviour to “Contains,” or alternatively, providing a configurable option that allows organizations to define their preferred default search behaviour.

Filter indication after adding a column to a table view vanishes.

After a recent Field Service update, the search behavior for requirements in the Schedule Board has changed. The filter now defaults to “Starts with” instead of the previous “Contains” behavior.

Although users can manually change the filter back to “Contains”, this setting is not persistent. After refreshing the requirements grid or navigating within the app, the filter automatically reverts to “Starts with.”

This change negatively impacts the user experience, as it introduces additional steps for users to locate the correct requirements during daily operations.

Restoring the previous “Contains” behavior or improving the persistence of the search filter would significantly enhance usability and improve the overall experience in the Schedule Board.