You’re offline. This is a read only version of the page.
Environment: Dynamics 365 Project Operations Core
Scenario:
We have multiple project task templates that need to be applied to a single project, sometimes the same template applied more than once. Our use cases can require up to several hundred tasks in total across all applied templates.
Problem:
We've evaluated the two available approaches but both have blockers:
Copy Project API (CopyProjectV3/V4): Only supports copying an entire project once to a target. It does not allow applying a second template to an already active project, as the target must be brand new with no prior activity.
Project Schedule Engine API (Operation Sets): Has the following limitations:
~200 operations per execution (tasks, labels, checklists, dependencies), effectively restricting usage to ~40 tasks per call
Operation Sets are not cleaned up on failure, blocking future executions due to the 10 Operation Sets per user limit
Question:
What is the recommended approach to efficiently apply multiple large project task templates with custom fields (potentially up to several hundred tasks) to a single project in Dynamics 365 Project Operations, given the above constraints? Are there patterns such as batching Operation Sets with cleanup logic, using background jobs, or alternative APIs that are recommended for this scale?
Any guidance, workarounds, or architectural patterns would be greatly appreciated. Thank you!
Share
Report
All responses (
Answers (
461
