Dynamics 365 Project Operations: Enable the Custom Dataverse Task Details Pane

With the general availability rollout of Roadmap ID 576877 (tracked in the Microsoft 365 Message Center as MC1464783), Microsoft has finally torn down that wall. Dynamics 365 Project Operations now offers an organization-level feature flag that swaps the rigid Project for the web iframe default for a customizable, Dataverse-backed model-driven side pane.

Here is a complete breakdown of how the customizable task details pane works, the architecture behind its synchronization engine, and what administrators need to know before flipping the switch.

Breaking Out of the Iframe: What Changed​

In Dynamics 365 Project Operations—spanning both Project Operations Integrated with ERP and Project Operations Core—the task grid serves as the operational nerve center for Work Breakdown Structures (WBS) and day-to-day scheduling. Historically, coupling Project for the web with Dataverse gave Microsoft a rapid, modern scheduling canvas, but it left a seam between the scheduling UI and Dataverse's rich customization layer.

According to Microsoft Learn documentation and the Dynamics 365 release plan, enabling the new feature changes the default click behavior in the task grid:

• Default Click Action (i icon): Selecting the information icon next to a task name now opens a customizable, Dataverse-hosted side pane rather than the locked Project for the web panel.
• In-Context Customization: Admins and makers can shape the task form to match internal business processes by adding, removing, or formatting fields, implementing custom validations, and triggering business flows directly from the grid context.
• Fallback Flexibility: Turning on the Dataverse pane does not obliterate the native experience. Users can still open the standard Microsoft Project for the web task details pane at any time via the Overflow menu, giving project managers access to both the custom Dataverse form and the standard Office task pane whenever needed.
• When Disabled: If the feature flag remains off, clicking the i icon continues to launch the standard, non-customizable Project for the web pane by default.

Summary: By shifting the primary task details flyout from an isolated iframe to a Dataverse-hosted side pane, organizations can finally surface custom task attributes without forcing users to switch tabs—while keeping the original Project pane one click away in the overflow menu.

Under the Hood: Data Sync, PSS, and Security Boundaries​

Anyone who has administered Dynamics 365 Project Operations knows that you cannot simply write directly to scheduling tables in Dataverse without respecting the underlying scheduling engine. Microsoft's official documentation on Microsoft Learn clarifies that the customizable side pane does not bypass the platform's scheduling safeguards.

When a user modifies task fields inside the new custom task details pane and hits save, the transaction follows a strict pipeline:

1. Project Scheduling Service (PSS) Commit: All edits made in the custom pane are saved using the Project Scheduling Service (PSS).
2. Automatic Dataverse Sync: Once processed by PSS, the changes automatically synchronize back to Microsoft Dataverse.
3. UI Recalculation: Derived and calculated fields are dynamically updated in the user interface to reflect the saved changes.
4. Error Handling: If a save operation runs afoul of a custom validation rule or a permission boundary, the system intercepts the failure and surfaces an explicit error message in the UI explaining what went wrong.

Equally important for enterprise governance is how the pane handles security. Because it is a native Dataverse model-driven experience, it strictly honors existing access controls:

• Users can only modify fields for which their security role already grants write permissions.
• All overarching task grid security and project access rules remain enforced.

Summary: The custom pane acts as a governed Dataverse front end that routes changes through the Project Scheduling Service, ensuring schedule integrity, calculated field updates, and role-based security remain intact.

Rollout Timeline and Version Context​

If you feel like you have seen this feature mentioned in release notes for nearly a year, you are not imagining things. The feature's journey through Microsoft's release pipeline spans several milestones:

• November 2025 (Early Core Appearance): Microsoft Learn's "What's new November 2025 - Project Operations Core" documentation first listed the Customize Task Pane feature alongside Dataverse environment version 4.161.0.1688.
• January 30, 2026 (Public Preview): According to the Dynamics 365 2025 release wave 2 plan and the Microsoft 365 Roadmap (ID 576877), the feature entered public preview in January 2026.
• September 2026 / October 2026 (General Availability): Microsoft Message Center advisory MC1464783 set the General Availability target for September 30, 2026, for Worldwide (Standard Multi-Tenant) web environments, and the roadmap item now officially carries a Launched status.

Summary: After debuting in early Core builds late last year and entering public preview in January 2026, the customizable task details pane has completed its journey to General Availability for Worldwide multi-tenant cloud environments.

How to Enable and Test the Customizable Task Details Pane​

Because changing the default task flyout alters the daily muscle memory of project managers, Microsoft ships this capability governed by an organization-level feature flag rather than forcing it on automatically. Administrators, makers, or analysts must explicitly enable it.

Step 1: Enable the Feature Control Flag​

According to Microsoft Learn's procedural guide, administrators can turn on the pane by navigating through the Project Operations settings area:

1. Open your Dynamics 365 Project Operations environment.
2. On the navigation ribbon, go to Settings > Parameters > Feature control.
3. Open the feature control drop-down list and locate the task pane customization option.

A Quick Admin Heads-Up on Naming: Microsoft's documentation contains a slight naming quirk across different pages. While the roadmap and release notes refer to the feature as Customize Task Pane or Enable Customize Task Pane, the step-by-step Microsoft Learn article explicitly instructs admins to select Enable Customize Task Pane dates in the drop-down list. When configuring your environment, look for Enable Customize Task Pane dates (or the closest matching Customize Task Pane label in your build) under Feature control.

Step 2: Verify the In-Grid Experience​

Once enabled at the organization level, test the behavior inside a non-production project first:

1. Open an active Project record and navigate to the Task grid tab.
2. Click the information (i) icon next to any task name.
3. Confirm that the custom Dataverse task details pane slides open on the side of the screen.
4. View and edit a task attribute, then save your changes and close the pane.
5. Verify that derived/calculated fields refresh properly on the grid and that the Overflow button still provides a working link to the native Project for the web task details pane.

What Makers Should Watch Out For​

While Microsoft's release plan highlights the ability to add fields, format views, and trigger workflows from the pane, Microsoft Learn's core procedural documentation stops short of listing every supported Dataverse field type or form-design constraint. Because edits must pass through the Project Scheduling Service (PSS), administrators and makers should thoroughly test any custom fields, business rules, or automated flows in a sandbox environment before deploying to production—paying special attention to how PSS handles validation errors and security role restrictions for standard team members.

Summary: Enabling the pane takes less than a minute via Project Parameters, but smart admins will verify the exact feature flag label in their tenant and test custom field saves against the Project Scheduling Service before rolling it out to end users.