Forum Discussion
Finding Slicer Min with Multiple Selections
- Anonymous8 years ago
Ultimately, I solved this by taking the table responsible for the slicer and offloading it into it's own table separate from the data getting filtered on. I was then able to run my min/max calculations on the offloaded table which was no longer being filtered down by my data as the relationship was 1 way from the offloaded table to the new table.
I believe I've found the solution. I offloaded the dates column alone within M:
- Right click column
- Add as new query
- Within the new query right click
- Convert to table
Then I input that column as the slicer and used the below equation to solve:
FormulaName = CALCULATE(MAX(OriginalTable[DateNumbers]), ALLEXCEPT(NewTable, NewTable[NewColumn]))
I'll circle back to confirm or delete this.
While the above post works in the example, it fails to work in the real file. In the example the table relationship is 1:1, no issue. In the real example the relationship is 1:Many, for some reason this causes Power Bi to error saying that because I'm choosing allexcept(newcolumn) and the new column is the only column in the table there is nothing to return. Any other ideas?
I've updated the example file to version 3 to illustrate the 1:* issue.