In my last article I build a resource focussed report for both Planner, and Planner Premium “plans”. In that article I removed the Roadmap tables, because they didn’t work anymore. But what if you want to report on the new portfolio feature, which is similar in so many ways? Let’s find out together!
I have vivid memories of the Project for the web – Project Accelerator report, that contained reports related to roadmaps… But for the life of me, I can’t find them anymore. Strange right?
I’ve downloaded the report multiple times. Thinking I might have already removed the pages and saved it. BUT it’s not there. Therefore I’m using the resource assignments report template, I shared before. And I’ll create a report page for you to patch that issue. In this blogpost I will tell you how to get the report tables.
Plans across named org environments
Creating the Portfolio is done either from Planner in Teams, or Planner.cloud.microsoft.com
Here’s one fun thing I noticed during this exploration. The Portfolio feature grabs information across multiple environments!
In the image above, I created a portfolio. And I added two projects. the first one is created in the default environment. And the “another environment project” came from the MPUG Project Accelerator environment I’ve build a while back.
Adding a project to the list, and following that up by adding phases (summaries or tasks) or Key dates (Milestone), results in a new Power Automate Flow. Meaning a portfolio with 20 projects, will result in 20 flows. Luckily the flow is small and fast, here, take a look at what it contains:
Once a day (unless refreshing the update manually from the portfolio) all projects inside the portfolio get updated information.
Oh, one downside. Only Premium plans are a part of the portfolio feature.
And then it hit me
The default org!
That would be where the Flows are stored, so it would make sence to have the roadmap records there as well.
Let’s build a nice report for Portfolios
In the report (and template) I’ve added an additional parameter specifically for the portfolios, because this set of tables only work in the default org. That way, you can report on your org specific projects AND have portfolios to boost.
The file I’m using is the same as in my last video and article.
The roadmap table, contains both roadmaps, and something new:
Great, now we know we need to rework the data a bit more, where we need to make sure to only work with the right types.
For the Roadmap table, make sure to have the Keep roadmap items as “2” to ensure we only have actual “Portfolios”
And we should also aim for a modern URL, so no longer referencing the Project url, but going full planner mode, changing the URL step to use:
https://planner.cloud.microsoft/webui/portfolio
The URL change should look like this:
Similar changes were needed on the roadmaprow table and the others as you can imagine. I won’t bore you with the details, the template v2 is available for subscribers to the newsletter.
Final notes
I hope you enjoyed reading this article on Portfolio reporting. It took me quite some time to dig up the tables and required values. And I learned a lot about the construct behind the tables that make up the portfolio feature.
If you’d like to get reporting based on my file, you can subscribe to my newsletter, the file is called “Assignments detail across plans v2.pbit” and it’s in the same folder as the previous file.
Just a reminder, this was the previous article, and I even included a video: