Extending #ProjectfortheWeb Part8 #PPM #CDS #MSDyn365 #PowerPlatform #MSProject #PowerApps #PowerAutomate #PowerAddicts

Following on from part 7 where we built the snapshot process, in this post we will show the process running then view the data. If you missed part 7 it can be found here: https://pwmather.wordpress.com/2020/03/12/extending-projectfortheweb-part7-ppm-cds-msdyn365-powerplatform-msproject-powerapps-powerautomate-poweraddicts/

On the stage process, for the stages where the flow was added you will see the Run Flow button:

Flow Action

This loads a modal window like below:

Run Flow

If you have issues with the window loading correctly try in Edge, in Chrome sometimes I would get the Login Successful message with nothing else displayed but this could have been due to my incognito session. Click Run Now to run the Flow. Click Done:

Flow Run

This process copies the project and task data into the custom project and task snapshot entities, this can be visualised in this functional Power BI report I have just thrown together to show the data in these new custom entities – it is not a visual report – it is functional:

Snapshot data

Now I will update the project by increasing some task durations, % complete and and the Overall RAG field then move the project on a stage in the process flow and take another snapshot:

Flow Action 2

Here is the refreshed data in the report with some examples of the data changing between snapshots outlined in red:

Snapshot data 2

This completes the business process flow stage driven snapshot example. Next up there is another quick example snapshot for when the project is updated as seen below – notice the new snapshot name in the rows outlined in red below:

Snapshot data 3

The Flow used for this is very similar to the stage driven snapshot example:

Flow Summary

Key differences are – this is triggered when a project record is updated:

Flow 1

Notice the attribute filters added to the trigger – so this example flow will only run then the description, overall status or estimated cost fields change. More fields can be added as needed. If no attribute filters are added, every time a task is created or updated, as that updates the project record, you will see lots of snapshots taken. To prevent lots of unnecessary snapshots, the attribute filters were added to the trigger. The next difference is in the action to create a project snapshot record – the snapshot name is different and the data used to create the record is from the trigger action:

Flow 2

The snapshot name is also different on the action used to create the task snapshot record:

Flow 3

That’s it – two simple processes using Power Automate Flows to add snapshot capabilities to your projects in Project for the web. More examples of adding features to Project for the web using the Power Platform coming up in part 9.

Comments are closed.

Blog at WordPress.com.

Up ↑

%d bloggers like this: