Dynamics Community Forum Thread Details

Hello Moritz,

Yes, this is a known and frustrating behavior that many Dynamics 365 Field Service users have experienced, particularly after updates. The system seems to have a tendency to re-introduce the out-of-the-box (OOB) requirement panels even when custom ones are configured.

Understanding Why This Happens (Likely Causes):

Update Overrides: The most probable cause is that during a Dynamics 365 Field Service update, the system's default configuration for the Schedule Board view settings might be reapplied, overwriting your custom settings for the requirement panels. This could be due to the way the update process handles default configurations or how it merges existing customizations with new versions.
Configuration Management Issue: There might be an underlying issue in how the system persistently saves and manages custom Schedule Board view settings, leading to a reset to default after certain events (like updates).
Specific Update Package Bug: It's also possible that a specific update package introduced a bug that inadvertently resets or adds the default requirement panels.

How to Address This Issue (Potential Solutions and Workarounds):

Unfortunately, there isn't a definitive, out-of-the-box setting to permanently prevent this from happening. However, here are several strategies and workarounds you can implement:

Regularly Re-Configure After Updates (Reactive but Necessary):
- The most immediate solution is to make it a routine task to check and re-configure your Schedule Board view settings after every Dynamics 365 Field Service update.
- Document your custom requirement panel configurations clearly so you can quickly reapply them.

Automate the Re-Configuration (More Proactive):
- Power Automate (Flow): You could potentially create a Power Automate flow that triggers on a recurring schedule (e.g., weekly or bi-weekly) or possibly after a system update (though reliably detecting updates as a trigger can be tricky). This flow could:
  - Retrieve the current Schedule Board view settings.
  - Check if the unwanted OOB requirement panel exists.
  - If it does, update the settings to remove it and save the configuration.
  - Challenge: Identifying the correct settings to modify via the Common Data Service (Dataverse) connector for the Schedule Board view can be complex. You'd need to understand the underlying entity and attribute structure that stores these settings.
- Client-Side Scripting (Unsupported but Sometimes Used Cautiously): While generally unsupported for configuration changes, you could potentially use client-side JavaScript (added as a web resource and triggered on the Schedule Board load) to inspect and modify the displayed requirement panels in the UI. However, this is highly fragile and prone to breaking with updates. Use this approach with extreme caution and understand the risks.

Investigate Underlying Configuration Entity (Advanced and Requires Technical Expertise):
- You would need to delve into the underlying Dataverse entities that store the Schedule Board view configurations. This might involve:
  - Identifying the specific entity (likely related to msdyn_scheduleboardsetting or similar).
  - Understanding the schema and how the requirement panels are stored (likely as a JSON or XML structure).
  - Potentially developing a tool or script (using the XrmToolBox or the Web API) to directly manipulate these settings and ensure only your custom panels are present.
- Challenge: This requires deep technical knowledge of the Field Service data model and is not officially supported for direct manipulation. Changes here could have unintended consequences.

Log a Support Ticket with Microsoft:
- Since this seems to be a recurring issue, especially after updates, it's crucial to report this behavior to Microsoft Support.
- Provide them with detailed steps to reproduce the issue, the version of Field Service you are using, and the frequency of the re-occurrence.
- By reporting it, you increase the chances of Microsoft acknowledging the issue and potentially providing a fix in a future update. They might also have insights into the underlying cause or a recommended workaround.

Monitor Release Notes:
- Keep a close eye on the release notes for every Dynamics 365 Field Service update. Look for any mentions of changes or fixes related to the Schedule Board or requirement panels. This might give you clues about why this is happening and if a permanent fix has been implemented.

Recommendation:

The most practical approach is likely a combination of:

Regularly re-configuring after updates.
Logging a support ticket with Microsoft to make them aware of the recurring issue.
Exploring the Power Automate option with caution and thorough testing if you have the technical resources to investigate the underlying data structure.

Directly manipulating the underlying configuration entities (option 3) should be a last resort due to the risk of unintended consequences and lack of official support. Client-side scripting (option 2) is also fragile and not recommended for configuration management.

By reporting the issue and implementing a routine check after updates, you can minimize the disruption caused by the re-appearance of the default requirement panel.

If my answer was helpful, please click Like, and if it solved your problem, please mark it as verified to help other community members find more. If you have further questions, please feel free to contact me.

My response was crafted with AI assistance and tailored to provide detailed and actionable guidance for your Microsoft Dynamics 365 query.

Regards,

Daivat Vartak

Community site session details

Schedule board settings are overwritten after updates / Requirement Panels BUG

Helpful resources

Quick Links

Responsible AI policies

Neeraj Kumar – Community Spotlight

Congratulations to the November Top 10 Community Leaders!

Leaderboard > Service | Customer Service, Contact Center, Field Service, Guides

Featured topics

Product updates