Dynamics 365 Project Operations: Unified Copy Project Setup, Field Controls and Empty Target Rules

With the launch of Microsoft roadmap item 576861 (Optimize Project Operations - Update key project fields using Copy project), also tracked in Microsoft 365 Message Center notifications such as MC1465233 and MC1465309, Microsoft has rolled out a unified project-copying experience for the web platform in Worldwide (Standard Multi-Tenant) cloud environments. Having entered public preview in late January 2026 and reached general availability in September 2026, this update gives project managers and administrators the ability to intercept and modify foundational project attributes before the duplication commits.

Here is a complete breakdown of what changes in the unified Copy Project workflow, why those specific fields matter so much to Dynamics 365 architecture, and the technical boundaries that administrators and developers still need to navigate.

The Old Bottleneck: Why Blind Cloning Broke Cross-Unit Templates​

To appreciate why a seemingly modest form dialog warrants attention from enterprise IT and project management offices (PMOs), you have to look at how Dynamics 365 Project Operations treats organizational ownership and time.

In the legacy Copy Project flow, selecting Copy Project immediately generated a new project record and copied over the source project's parameters. Because certain foundational columns in Project Operations dictate currency, cost/sales price lists, accounting ledgers, and task scheduling math, the platform locks several of these fields once a project is created or selected.

Under the old behavior, if a global consulting firm maintained a "Gold Standard ERP Implementation" template project under its US Contracting Unit and US legal entity, a project manager in the UK or Germany couldn't simply click Copy Project and switch the Owning Company or Contracting Unit on the fly. You either had to maintain redundant templates for every organizational unit and scheduling mode, or build custom Power Automate flows and plugins calling the underlying Dataverse APIs just to pre-stage a blank project with the right headers before copying the tasks over.

What the Unified Copy Project Experience Adds​

Once an administrator, maker, or analyst enables this feature in the environment's feature control settings, the standard duplication button transitions to the new unified copy project experience. Instead of blindly cloning the header record, the workflow introduces two major capabilities:

1. Flexible Target Selection (New vs. Existing Empty Project): Users can choose either Copy to New Project or Copy to Existing Project. When copying to an existing record, the user selects the destination project directly during the copy process from a list of eligible empty projects.
2. Pre-Copy Attribute Configuration: When duplicating a project, users can explicitly define key project attributes prior to creation. According to Microsoft's release plan documentation, the specific fields exposed for modification include:
   • Contracting Unit: Defines the organizational unit or division responsible for delivering the project, which governs internal resource costing and organizational alignment.
   • Owning Company: Crucial for Project Operations Integrated with ERP (non-stocked/resource-based scenarios), where a project must be tied to a specific legal entity.
   • Schedule Mode: Lets project managers dictate the scheduling engine behavior (such as Fixed Duration, Fixed Effort, or Fixed Units) at the outset rather than being stuck with the source project's scheduling math.
   • Calendar Template: Determines the working hours, workdays, and holiday schedules that the scheduling engine will use when calculating task durations for the new project.

When a user selects Copy to New Project, a quick-create form appears with these options and configurations right up front, ensuring that custom inputs are captured for fields that immediately lock once the project record is instantiated. If the user selects Copy to Existing Project, a dialog box prompts them to pick an eligible target project and specify how project team members should be handled.

Section Summary: The unified Copy Project experience replaces automatic, uneditable header duplication with an interactive prompt. Once enabled by an admin in feature control settings, users can route copies into either a brand-new project or an eligible empty project while configuring the Contracting Unit, Owning Company, Schedule Mode, and Calendar Template upfront.

Under the Hood: What Gets Copied Across Deployment Types​

While the new prompt standardizes how you initiate a copy, what actually travels from the source project to the destination depends heavily on which variant of Dynamics 365 Project Operations your organization runs. Microsoft supports three primary deployment models—Project Operations Non-Stocked Materials (integrated with finance and operations ERP), Project Operations Core (lite deployment dealing with pro-forma invoicing in Dataverse), and Project for the Web.

According to Microsoft Learn documentation for the Copy Project operation, a source project must contain at least one task before it can be copied (a feature that also works for externally scheduled projects). When executed, the process copies six major data buckets:

• Project properties
• Work breakdown structure (WBS)
• Project team members (except in Project for the Web, which does not copy team members or assignments)
• Project estimates across Labor, Expense, and Material lines
• Project checklists
• Project buckets

However, not every project property column exists or copies across all three versions. Below is how Microsoft documents property inheritance across the platform variants:

Note on Dates: Microsoft notes that Estimated Start Date defaults to the date the project is created from the copy (unless a target date is already present on a target entity), and Estimated Finish Date automatically recalculates relative to that new start date. Furthermore, quotes and contracts are never linked to the destination project during a copy operation; commercial linkage must always be established separately.

Section Summary: A project requires at least one task to be copied, and while WBS tasks, checklists, and buckets move across seamlessly, financial estimates, team assignments, and legal-entity properties like Owning Company depend on whether you are running the ERP-integrated, Core, or Project for the Web deployment.

Operational Realities and "Gotchas" for Admins and Developers​

Even with the cleaner user interface, copying a complex project in Dataverse is not an instantaneous database row insert. Enterprise administrators and solution architects should keep four technical guardrails in mind when rolling this feature out to end users:

1. Asynchronous Locks and Schedule Recalculation​

Because copying a project duplicates the header record alongside potentially hundreds of related WBS tasks, dependencies, checklists, and estimate lines, it executes as a long-running asynchronous operation. Once initiated, the destination project page is locked for editing until the background system job finishes.

Additionally, when the resource-loaded WBS is duplicated in Project Operations, the system automatically strips out named human resources and replaces them with generic resources representing their roles (with the sole exception of the Project Manager, who must remain a named user). If a named engineer on the source project had a custom work calendar (say, four 10-hour days) that differs from the generic resource's calendar or the newly selected Calendar Template, the scheduling engine will recalculate the schedule upon copy, which can alter task durations on the destination project.

2. Strict Rules for an "Existing Empty Project"​

The ability to copy into an existing project is particularly handy when a project record is auto-generated upstream—for instance, when winning a CRM Opportunity or Quote automatically spins up a shell project record. However, "existing empty project" has a strict technical definition in Project Operations.

According to Microsoft's developer validation rules for the underlying msdyn_CopyProjectV3 and msdyn_CopyProjectV4 custom actions, a target project is only eligible if:

• It is brand new and has zero previous activity—Remarkably, even clicking into and opening the Tasks tab on the target project initializes background scheduling structures and disqualifies the project as an empty target.
• It has never had a previous copy or import requested against it, and is not in a Failed status.

In short, this is a template-hydration tool for untouched project shells, not a way to merge tasks into an active project or overwrite a project that went off the rails.

3. Customizing Copied Columns and Team Mappings (V3 vs. V4 APIs)​

What if your organization has custom fields on the Project or Project Task tables that also need to carry over during a copy? Adding them to the UI form isn't enough. Microsoft's architecture controls copied attributes through specific Dataverse views:

• Project Task Custom Columns: Add custom task fields to the Copy Project Task Columns view on the Project Task table, and CopyProjectV3 or CopyProjectV4 will automatically include them.
• Project Entity Custom Columns: Add custom project header fields to the Copy Project Columns view on the Project entity. If you are automating copies via plugins or Power Automate flows, note that you must also call the CopyProjectEntityAttributesRequest API separately alongside your CopyProjectV3 or CopyProjectV4 call to pull those custom view columns across.

For developers building custom template engines, Microsoft's newer msdyn_CopyProjectV4 action expands on V3 by introducing a TeamMemberOption parameter (0 to skip team members, 1 to copy as generic resources, or 2 to map source team members directly to a specified collection of named or generic target resources via a TeamMembersMapping JSON dictionary). That mirrors the team-member selection prompt now surfacing in the Copy to Existing Project UI dialog.

How to Roll This Out in Your Environment​

Because Microsoft classified roadmap item 576861 as Enabled by admins/makers/marketers for end users, the new unified copy experience will not necessarily ambush your project managers overnight without an admin flipping the switch.

To adopt the update safely:

1. Enable in a Sandbox First: Locate the unified copy project toggle within your Project Operations feature control settings in a non-production environment and turn it on.
2. Test Variant-Specific Field Combinations: Have a lead project manager copy a multi-task project into a new project while changing the Contracting Unit, Owning Company (if on the Non-Stocked ERP variant), Schedule Mode, and Calendar Template. Verify that the downstream price lists, currency defaults, and WBS task durations recalculate as expected once the asynchronous lock clears.
3. Train Users on the "Don't Touch the Tasks Tab" Rule: If your workflow relies on Copy to Existing Project, make sure project managers know not to open the Tasks tab on a newly created shell project before running the copy action, or the target project will fail eligibility validation.

Section Summary: While the unified Copy Project feature removes a longstanding administrative headache in Dynamics 365 Project Operations, it still operates within Dataverse's asynchronous copy engine. Administrators should enable the feature in feature control settings, verify how custom columns behave in the Copy Project Columns views, and remind users that existing target projects must remain completely untouched prior to copying.