Get certified for free when you join Fabric Data Days 2026 and dive into Fabric, Power BI, SQL, AI, and other essential data skills.
Join nowTry your skills in the Power BI Dataviz World Championship! Round one ends June 26. Join now
So we want to create a BI directory for our organization (ideally another powerBI report) with "about" pages for each report/dashboard/scorecard and any other content we have deployed in production apps. Within each app, the relevant about pages will be made available as well for the selected app users. While this is somewhat implementable by using "Add a link" option under "Content" tab when "managing" an app along with the ability to include a link to an individual page within a report from another workspace, clicking the about page on that app will still take them to the main "directory", outside of the app. While this solution works, it does not feel elegant or clean. Anyone have any better ideas?
P.S. Our strategy department has decided to make it known organization wide what Power BI items we have available regardless of whether someone has access to them or not. Hence this question. Thank you.
Solved! Go to Solution.
Hi,
What if you...
1. Created a reference table where you maintained all your About information
2. Stored that in a central shared drive for your team
3. Queried that table in each of your reports
4. Create the about page in your reports and show that table, and filter accordingly for the record or show all as a directory
Then, as you update the ref file, it will reflect automatically when you refresh the reports.
Hi,
What if you...
1. Created a reference table where you maintained all your About information
2. Stored that in a central shared drive for your team
3. Queried that table in each of your reports
4. Create the about page in your reports and show that table, and filter accordingly for the record or show all as a directory
Then, as you update the ref file, it will reflect automatically when you refresh the reports.
Thank you. The "about" page data will infact be stored on OneLake hub as a relational model drawing from a SQL table. I was just hoping to avoid double work of creating a master "about" "directory" for the entire organization and then rebuild those pages in each of the reports/apps again.
Hi @pborah
As it stands today, clicking on any link within any power BI report will open it in another tab. So while I understand this does not feel super elegant or clean, it is currently the way it is. You can create or vote for an idea here. https://aka.ms/FabricIdeas
Don't miss out on Data Days, June 15 through August 7. Learn Fabric, Power BI, SQL, AI and more.
Check out the May 2026 Power BI update to learn about new features.
| User | Count |
|---|---|
| 17 | |
| 11 | |
| 11 | |
| 8 | |
| 8 |
| User | Count |
|---|---|
| 40 | |
| 36 | |
| 35 | |
| 35 | |
| 20 |