Summary

In Schedule Assistant, Weekly view can render resource availability in a way that appears misleading: availability (or partial hours such as “1h available”) can appear on non-working days (e.g., Sunday) or look centred/split across adjacent days, even when the resource calendar is correctly configured. The behavior becomes more prominent when the Search start/Search end window crosses day/week boundaries and/or when time zone context changes based on how the assistant is launched.

This is not a booking logic error (booking constraints still apply), but it creates a significant usability and adoption risk, because dispatchers interpret the UI as indicating “bookable availability” on days the resource is not actually working.

Problem Statement (What users experience)

A resource with standard working hours (e.g., Mon–Fri 9–5) can show:

• Partial “availability” in Sunday in Weekly view (e.g., “1h available”).
• An 8-hour workday that appears visually shifted/centred across two days.

Weekly totals can appear inconsistent (e.g., 8h, 32h, 40h) depending on the active Search start/Search end window, but the UI doesn’t clearly communicate that the totals are “within the search window” rather than “weekly capacity.”

Technical Cause (What’s happening under the hood)

This appears to be a rendering/visualization issue driven by how Schedule Assistant:

• Applies Search start / Search end as the evaluation window, which defaults to the requirement’s From/To dates and can be adjusted. In Weekly view, totals are therefore constrained to the working days that fall inside the search window

Official document: https://learn.microsoft.com/en-us/dynamics365/field-service/schedule-assistant

• Uses a time zone context that depends on launch path (derived from the requirement when launched from a schedulable entity/requirement; derived from schedule board settings when launched from the board)

Official document: https://learn.microsoft.com/en-us/dynamics365/field-service/schedule-assistant

• In Time Zone Agnostic mode, normalizes times to UTC and displays on a Gantt timeline that is always set to UTC

Official document: https://learn.microsoft.com/en-us/dynamics365/field-service/schedule-timezone-agnostic.

• Weekly view also introduces user expectations around week boundaries (e.g., week starts on Sunday) which can amplify confusion when a search window intersects boundaries

Official document: https://learn.microsoft.com/en-us/dynamics365/field-service/work-with-schedule-board.

Even when users understand the underlying rules, the UI can still present an unreadable or misleading view for dispatchers.

Steps to Reproduce (Reliable)

1. Create a Bookable Resource with working hours Mon–Fri 9:00–17:00 (no weekends).
2. Open Schedule Board → Schedule Assistant → Weekly view.
3. Use a search window that crosses a boundary (example patterns):
4. Search start late Sunday / Search end early Monday (or vice versa), OR
5. Search range that spans partial days across weeks.
6. Observe that Weekly view may show:

• Partial availability on Sunday (e.g., “1h available”) even though Sunday is a non-working day for the resource.
• Availability that looks visually shifted across adjacent day columns.

Actual Result

• UI shows “availability” indicators/hours on non-working days or across boundaries, which is interpreted as bookable capacity.
• Weekly totals vary depending on the search window but the UI does not sufficiently explain the relationship.

Expected Result

• Weekly view should not visually imply that a resource is available on a non-working day unless their calendar includes working hours for that day.
• Weekly totals should be clearly labeled as either:

“Availability within search window” vs “Resource weekly capacity”, OR

The assistant should provide an option to automatically expand the search window to the full week when in Weekly view.

Business Impact

• Many dispatchers and resource managers rely heavily on the Schedule Assistant UI.
• Misleading “availability” erodes trust, slows scheduling, increases training effort, and creates a perception that the product is unreliable or unusable for global/project-based organizations.
• This directly impacts adoption, repeat usage, and customer confidence, especially for enterprise program rollouts and partners delivering Project Operations scheduling solutions.

Suggested Product Improvements:

A. Rendering/UX fixes

1. In Weekly view, snap availability bars and hour badges to working-day boundaries, preventing hours from appearing in non-working day columns unless the calendar includes those hours.
2. Provide a clear UI indicator/tooltip when availability is affected by time zone/search window boundaries:

• e.g., “Availability shown is constrained to Search start/end and rendered in the selected board/requirement time zone. Partial hours may appear at boundaries.”

B. Search window clarity

3. Add a “Expand to full week” button (or auto-expand when switching to Weekly view).

4. Label weekly totals explicitly as “within Search window” or provide an optional “show full-week capacity” overlay.

C. Time zone clarity

5. Show the effective time zone used for Schedule Assistant results prominently (and the source: requirement vs board settings), aligning with documented derivation behavior (https://learn.microsoft.com/en-us/dynamics365/field-service/schedule-assistant).

6. When Time Zone Agnostic is enabled, clearly communicate that results are normalized to UTC as documented (https://learn.microsoft.com/en-us/dynamics365/field-service/schedule-timezone-agnostic).

Workaround (Current)

• Users must manually adjust Search start/end to align with week boundaries (Mon–Fri) and interpret partial-day artifacts as boundary effects. This is not practical for daily dispatch operations.