Dynamics Project Service – Using Stage Name in v3.0

If you are like me, you work for a company that uses Dynamics Project Service. You recently upgraded from v2 to v3.0. You may have noticed that there is no longer a workflow that updates the Project Stage Name based upon Active Stage in the Business Process Flow.

You thought “OK, I will just create a workflow on the Project Stages Business Process change of active stage.” You were probably greeted with a similar message when trying to update the project record with the active stage name:

In a last ditch effort to preserve the sanity and beautiful PowerBI dashboard of our Director of Operations (which was based upon our project stages), I created a Flow to do the same thing. Below are some steps I followed to get the Stage Name to populate once again.

First off, you may need to recreate this Flow on Create and Update of the Project Stages entity. This is the entity for the Project Business Process Flow.

When a Project Stage record is updated:

Get the Active Stage related to the Project Stage which was updated:

Get the Project Record related to the Project Stage which was updated:

Update the Project Record:

Voila! We have a working Stage Name Field! You can recreate this process in a new implementation of Project Service as well. You would need to create your own Single Line of Text field to replace the Stage Name field.

Author: Bernie Thibeault

What I love most about Dynamics 365 is how it streamlines processes for businesses of all sizes. Every organization is unique, but they all have the same need to get more done in less time. Dynamics 365 is the solution to do that. I'm a skilled listener who knows how to get beneath the surface and hone in on exactly what clients need to get out of Dynamics 365, making him one of the most valuable additions to any team.