Forum Discussion
percentage slicer
No, the idea of a selection based table is that you can get your measures to check the filter context of the selection table and alter their output accordingly. The use of "MIN" or "MAX" handle that while you expect the table to only ever have a single row, it also covers when nothing is selected
Here is another method. Create a Confidence Table. This table will have 3 columns:
Column 1: Numeric ID from 1 onwards as whole numbers
Column 2: The text to display in your slicer
Column 3: Numeric effect on your formula
Now you set up your slicer to use column 2 of that table. Then your forecast measure can be affected by Column 3 using a MIN statement.
For example, lets say that you suggest "If my forecast confidence is <75%, multiply the forecast by 1.1. If my forecast is between 75% and 125%, do nothing, and lastly if its above 125% we will multiply by 0.9.
So my Columns in the selection table would have the IDs and Text to display the ranges (or individual values) and then column 3 would contain 1.1, 1, or 0.9.
Now my Adjustment Forecast measure would be
Forecast = [Old Forecast Measure] * MIN('Selection Table'[Column3Name])
EDIT: Something to note. Side as ID 1 for whatever you want the default to be. Whenever nothing is selection, 1 will be your minimum value, thus your default.
Thank you Anonymous, but I@m not sure I entirely understand. Would I create a relationship between this new table and my existing data?
thanks
No, the idea of a selection based table is that you can get your measures to check the filter context of the selection table and alter their output accordingly. The use of "MIN" or "MAX" handle that while you expect the table to only ever have a single row, it also covers when nothing is selected
