Schedule APIs reach GA in Dynamics 365 Project Operations

April 13 2021

As Microsoft transitions its project business management software story to the still-new Dynamics 365 Project Operations, customers and consultants alike must adjust to new ways of building solutions.

In the case of API-based access, we were accustomed to an approach offered by the predecessor to Project Operations, Dynamics 365 Project Service Automation (PSA). PSA  allowed users to call APIs to do CUD operations (Create, Update and Delete) on entities like Project, Project Task, Resource Assignment, Project Team Member and Project Task Dependency. 

With the introduction of Project Operations, architectural differences have meant we lost that API access. For customers, the need for API access remained strong and their requests are at a peak on today's projects.

Introducing the Schedule API

Microsoft has developed a new set of APIs known as the Schedule APIs to provide Project Operations customers with CUD access to key project-related entities, with some differences.

Schedule APIs call on Dataverse, which serves as the database layer for Project Operations. The new APIs works in a fundamentally different way because in Project Operations the WBS  is now managed by P4W (Project for the Web), which is a different engine than PSA. Schedule API now provides that critical line of communications between PO and P4W.

Here is a list of the entities covered by the Schedule API with their logical names:

 Microsoft Dynamics 365 Project Operations Schedule APIs logical entities

The table below lists all the operations Microsoft currently supports: 

 Microsoft Dynamics 365 Project Operations Schedule APIs details

A few final notes about the Schedule APIs for Project Operations:

  • Resource Assignments cannot be updated. Instead, Project Operations deletes the existing entity and creates a new one. So there is no support for updating a Resource Assignment. The same thing applies to Task Dependency. 
  • These APIs can be called with entity objects that including custom fields.  
  • The Id property is optional. If you provide one, Project Operations will try to use it. The API will throw an exception if it cannot use the id you provide. If you don’t provide one, the system will generate one. 

The Scheduling API will be available in the Project Operations release.

FREE Membership Required to View Full Content:

Become a MemberLogin
Joining gives you free, unlimited access to news, analysis, white papers, case studies, product brochures, and more, and it’s all FREE. You’ll also have the option to receive periodic email newsletters with the latest relevant articles and content updates. Learn more about us here
About Kuldeep Gupta

Kuldeep Gupta is a Microsoft MVP. 

More about Kuldeep Gupta