Earn the coveted Fabric Analytics Engineer certification. 100% off your exam for a limited time only!
Hi,
For our sales dep. I'm working on a report in which we compare the signed and expected (hot) deals against the target. The idea is to have slicers in place to select the status of a deal (for example, "signed, won") and to select if the deal is a hot deal or not. If the hot deal slicer is set to "yes", then the result set should show the deals with the selected statusses + all deals with hot deal = yes (regardless the status). So the slicers combined must use "OR" logic instead of the default "AND" logic. I'm trying to visualize the results (from table Query1) in a radial gauge visual.
To make this work I created 2 unlinked tables with the statuses and the hot deal boolean and a measure "FilterMeasure" with the following DAX:
FilterMeasure = CALCULATE((MAX(Query1[Status]) = SELECTEDVALUE(StatusTable[Status])) +
(MAX(Query1[HotDeal]) = SELECTEDVALUE(HotDealTable[Value])))
Solved! Go to Solution.
Here are two approaches you might consider. Create a separate measure with the filter logic, and use a Fields parameter to allow the user to toggle between the base measure and the measure with the filter logic.
Alternatively, you could add columns to your fact table that correspond to the two disconnected tables. This would enable you to create relationships (the disconnected tables would become dimension tables in a star schema), allowing you to filter on Hot Deal, for example.
Proud to be a Super User!
Hi @DataInsights,
Thank you! The second alternative did work for us. We created a calculated column in the fact table and created a slicer for that.
Here are two approaches you might consider. Create a separate measure with the filter logic, and use a Fields parameter to allow the user to toggle between the base measure and the measure with the filter logic.
Alternatively, you could add columns to your fact table that correspond to the two disconnected tables. This would enable you to create relationships (the disconnected tables would become dimension tables in a star schema), allowing you to filter on Hot Deal, for example.
Proud to be a Super User!
User | Count |
---|---|
41 | |
27 | |
23 | |
18 | |
15 |
User | Count |
---|---|
54 | |
35 | |
19 | |
18 | |
15 |