This is best Fabric, Power BI, SQL and AI community event. How do we know? The last event sold out! Save €200 with code FABCMTY200.
Register nowA new Data Days event is coming soon! This time we’re going bigger than ever. Fabric, Power BI, SQL, AI and more. Don't miss out.
Hi community, In this time I going to need to "create a new function", this object should be return the name of the report. I mean..
PBIX file constains "Report A" and "Report B", if the user is inside the "Report A" the function should be "The user is in Report A", the same case for "Report B".
I know there isn't function yet. So any way to solve this issue? any tips.
Thanks in advance.
Solved! Go to Solution.
Hi @Peter_23
There isn't a native DAX function like REPORTNAME() that can dynamically read the tab or report name, but you can achieve this behavior using a couple of workarounds depending on how you structure your file.
If "Report A" and "Report B" are separate pages inside the same PBIX file, the easiest trick is to use page-level filters or a disconnected navigation table. You can create a small disconnected table containing your page names, use that table to build a custom navigation menu or slicer, and then use SELECTEDVALUE() in your measure.
Alternatively, you can hardcode a specific measure on each individual page to identify it, or use the Page Name option found in the standard page navigator visual conditional formatting settings to dynamically capture where the user is looking.
If "Report A" and "Report B" are completely separate report files published to the Power BI Service that share the same semantic model, you can use the USERPRINCIPALNAME() or CUSTOMDATA() functions to pass environmental context, but the most robust method for separate reports is to simply use a localized table or parameter in each specific PBIX file before publishing.
Thanks @Poojara_D12 @Yuliia_Mai @ryan_mayu I'm going to use hidden measure with slicer, I voted for the function!!
Hi @Peter_23
There isn't a native DAX function like REPORTNAME() that can dynamically read the tab or report name, but you can achieve this behavior using a couple of workarounds depending on how you structure your file.
If "Report A" and "Report B" are separate pages inside the same PBIX file, the easiest trick is to use page-level filters or a disconnected navigation table. You can create a small disconnected table containing your page names, use that table to build a custom navigation menu or slicer, and then use SELECTEDVALUE() in your measure.
Alternatively, you can hardcode a specific measure on each individual page to identify it, or use the Page Name option found in the standard page navigator visual conditional formatting settings to dynamically capture where the user is looking.
If "Report A" and "Report B" are completely separate report files published to the Power BI Service that share the same semantic model, you can use the USERPRINCIPALNAME() or CUSTOMDATA() functions to pass environmental context, but the most robust method for separate reports is to simply use a localized table or parameter in each specific PBIX file before publishing.
Hi @Peter_23
There's no DAX function for this yet, it's actually a long-standing feature request on the Power BI Ideas forum with a lot of votes but still no implementation. The only practical workaround is to create a what-if parameter or a simple DAX measure with a hardcoded value per report:
Report Name = "Report A"Not elegant, but it works. The measure then travels with that specific report and you can use it in any visual or dynamic title.
If this is something you need across many reports it's worth upvoting the idea here: https://ideas.fabric.microsoft.com/ideas/idea/?ideaid=9b0aed22-be8a-4483-af35-c91b8fe0b79e
then you need to create two reports and use rls to control the display data.
https://learn.microsoft.com/en-us/power-bi/guidance/rls-guidance?wt.mc_id=DP-MVP-5004616
Proud to be a Super User!
Check out the May 2026 Power BI update to learn about new features.
Sign up to receive a private message when registration opens and key events begin.
If you have recently started exploring Fabric, we'd love to hear how it's going. Your feedback can help with product improvements.
| User | Count |
|---|---|
| 28 | |
| 28 | |
| 26 | |
| 20 | |
| 16 |
| User | Count |
|---|---|
| 52 | |
| 47 | |
| 39 | |
| 21 | |
| 20 |