Starting December 3, join live sessions with database experts and the Microsoft product team to learn just how easy it is to get started
Learn moreGet certified in Microsoft Fabric—for free! For a limited time, get a free DP-600 exam voucher to use by the end of 2024. Register now
Hi guys! Relative newbie here, been working with PBI for the last six months or so, previously coming from a Qlik background.
I have a problem that I'm stumped trying to resolve. I've scoured the various forums and blogs looking for a possible answer, but haven't found anything yet.
I have a star-schema data model with a date table that has two possible relationships to my fact table. One relationship is marked as active, and the other inactive.
I've learned how to use USERELATIONSHIP() in my measures to show aggregated scalar values correctly. But my issue is that there doesn't appear to be any way to deploy USERELATIONSHIP() to globally apply to all visuals throughout the entire report. Essentially, I want one toggle button/filter to trigger a global USERELATIONSHIP() at the data model level, with the entire report updating appropriately.
Right now my toggle is built as a filter, but I'm not married to that if there's a better way (button? slicer?).
And here's what my (correctly functioning) Measures look like:
Solved! Go to Solution.
well, you have a lot of measures that return specific values, in case there is only 1 possible scalar value, for example: SELECTEDVALUE(). Whatever tooltip you are using, if it direct to a visual in Power BI that you have put there implicit measures, you can replace them with explicit measures, and than the userelationship will kick in 🙂
You can't do that without a measure, you can't change globally the active relatioship. It's only per measure or group of measures with use of calculation groups
Thanks for the quick replies! But - how do I use USERELATIONSHIP() without an aggregation/measure? My report has a "Detail" page that uses a Table visual to display all of the rows from the Fact table that meet my filter criteria. This needs to be row-level detail, not aggregated by dimensions - which means I can't use measures. But I still need for all of the filter criteria to apply, including which date relationship to use.
Perhaps there's a way to construct a measure that doesn't do any aggregation, but simply returns a specific cell (row/column) from the Fact table?
well, you have a lot of measures that return specific values, in case there is only 1 possible scalar value, for example: SELECTEDVALUE(). Whatever tooltip you are using, if it direct to a visual in Power BI that you have put there implicit measures, you can replace them with explicit measures, and than the userelationship will kick in 🙂
You can't do that without a measure, you can't change globally the active relatioship. It's only per measure or group of measures with use of calculation groups
Not sure exactly what you meant by globally, but if you meant you want the option of a toggle that will effect multiple measures at once you can use Calculation Groups.
You will have 2 calculation items:
1. SELECTEDMESURE()
2. CALCULATE(SELECTEDMESURE(), USERELATIONSHIP(...) )
You can also wrap up CI no 2 to only affect / not affect specific measures with an IF condition.
Hope that helps
@ctmullins , One option is bookmarks and button, another create all measure using the slicer values like measure slicer
example
measure slicer
https://www.youtube.com/watch?v=b9352Vxuj-M
https://community.powerbi.com/t5/Desktop/Slicer-MTD-QTD-YTD-to-filter-dates-using-the-slicer/td-p/50...
https://radacad.com/change-the-column-or-measure-value-in-a-power-bi-visual-by-selection-of-the-slic...
example Bookmarks
https://radacad.com/bookmarks-and-buttons-making-power-bi-charts-even-more-interactive
https://docs.microsoft.com/en-us/power-bi/desktop-bookmarks
Starting December 3, join live sessions with database experts and the Fabric product team to learn just how easy it is to get started.
March 31 - April 2, 2025, in Las Vegas, Nevada. Use code MSCUST for a $150 discount! Early Bird pricing ends December 9th.
User | Count |
---|---|
92 | |
86 | |
83 | |
66 | |
49 |
User | Count |
---|---|
140 | |
114 | |
108 | |
64 | |
60 |