This time we’re going bigger than ever. Fabric, Power BI, SQL, AI and more. We're covering it all. You won't want to miss it.
Learn moreGet Fabric Certified for FREE during AI Skills Fest. This week only. Secure your voucher now.
I have 3 measure in matrix on page A. I want to create a page D, that user will drill htough from Page A from one o this 3 measures. Can I catch on the destination DT page D which of thre measures was used for drill through?
Thank you
PS: I know how to achive this by creating one supermeasure with all my 3 measures combined and using additional isolated table to split the measures using switch in supermeasure, but that approach brings some other problems ....
Solved! Go to Solution.
Hey @EduardD ,
No the destination page cannot natively detect which measure was used to trigger the drill-through.
Power BI drill-through only propagates filter context from fields placed in the Drillthrough. The identity of the measure whose cell was right-clicked is not part of that context and is not exposed to the destination page. There is no system function, DAX construct, or built-in property that returns "the source measure" on the target page. This is also why Microsoft's own guidance on Field Parameters explicitly states that a field parameter cannot be used as the linked field of a drill-through page, with the recommended workaround being to reference the underlying fields individually.
In other words, the disconnected-table + SWITCH pattern you described is not just one option among many. It is effectively the canonical workaround for this exact limitation, because it converts the missing "measure identity" into an actual filter on a real column, which is something drill-through can carry.
For Detailed Information:
Best Regards,
Nasif Azam
Hey @EduardD ,
No the destination page cannot natively detect which measure was used to trigger the drill-through.
Power BI drill-through only propagates filter context from fields placed in the Drillthrough. The identity of the measure whose cell was right-clicked is not part of that context and is not exposed to the destination page. There is no system function, DAX construct, or built-in property that returns "the source measure" on the target page. This is also why Microsoft's own guidance on Field Parameters explicitly states that a field parameter cannot be used as the linked field of a drill-through page, with the recommended workaround being to reference the underlying fields individually.
In other words, the disconnected-table + SWITCH pattern you described is not just one option among many. It is effectively the canonical workaround for this exact limitation, because it converts the missing "measure identity" into an actual filter on a real column, which is something drill-through can carry.
For Detailed Information:
Best Regards,
Nasif Azam
Hi @EduardD
Power BI doesn’t know which measure was selected for the drillthrough. It only recognizes the dimension values in the selected row. So if multiple measures correspond to the same row value (e.g., “A”), only A will be passed to the destination page - assuming it’s used as the drillthrough field. And yes, the only workaround is to rely on what’s in your PS.
Hi @EduardD
Power BI does not provide a way to measure triggering a drillthrough as drillthrough only passes filter context of columns and not a measure context.
To my knowledge you might need to externalize the measure selection using a disconnected table or field parameter and use that as part of the drillthrough context
"Power BI does not provide a way to measure triggering a drillthrough as drillthrough only passes filter context of columns and not a measure context."
not exactly, you can use measure for DT, and Filter context is passed
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 |
|---|---|
| 24 | |
| 24 | |
| 21 | |
| 21 | |
| 18 |
| User | Count |
|---|---|
| 56 | |
| 53 | |
| 49 | |
| 26 | |
| 26 |