Forum Discussion
Scenario Help
Hi charles_o,
You can try the approach of McCow. Another method.
1. Create a middle table for all the scenario.
Scenario
Low Base High Low,Base Low,High Base,High Low,Base,High 2. Create a table for slicer.
SlicerScenario
Low Low Base Base High High Low Low,Base Base Low,Base Low Low,High High Low,High Base Base,High High Base,High Low Low,Base,High Base Low,Base,High High Low,Base,High
3. Create relationships and change the filter direction to Both.
Best Regards,
Dale
Hi charles_o,
You can try the approach of McCow. Another method.
1. Create a middle table for all the scenario.
Scenario
| Low |
| Base |
| High |
| Low,Base |
| Low,High |
| Base,High |
| Low,Base,High |
2. Create a table for slicer.
SlicerScenario
| Low | Low |
| Base | Base |
| High | High |
| Low | Low,Base |
| Base | Low,Base |
| Low | Low,High |
| High | Low,High |
| Base | Base,High |
| High | Base,High |
| Low | Low,Base,High |
| Base | Low,Base,High |
| High | Low,Base,High |
3. Create relationships and change the filter direction to Both.
Best Regards,
Dale
Fantatic!
Thanks v-jiascu-msft
I change a little "Scenario" column:
Scenario =
IF(SEARCH("likely";[Likelyhood];1;0)>0 || SEARCH("hopeful";[Likelyhood];1;0)>0 ;"High";
IF(SEARCH("expected";[Likelyhood];1;0)>0;"Base";
IF(SEARCH("certain";[Likelyhood];1;0)>0;"Low";
"Error"
)//high
)//base
)//low
And THIS is a cAsE independent solution.
Best regs
I think we are misunderstanding this a bit.
Included in A CERTAIN High, Base, Low B EXPECTED High, Base C LIKELY High D HOPEFUL High Think about it like this
Low = A
Base = A + B
High = A + B+ C + D
So when I select "High", the data for Low and Base must also be included.
Yes, charles_o, right!
charles_o wrote:
......So when I select "High", the data for Low and Base must also be included.
And I don't see the collision. Our last solution is completely adjustable. All possible combinations must be in the table "Solution" described. I personally include this solution in my personally DAX-gems (thank v-jiascu-msft). Or somewhere exist some trouble? Specify pls
Yes, charles_o, right!
charles_o wrote:
......So when I select "High", the data for Low and Base must also be included.
And I don't see the collision. Our last solution is completely adjustable. All possible combinations must be in the table "Solution" described. I personally include this solution in my personally DAX-gems (thank v-jiascu-msft). Or somewhere exist some trouble? Do you can specify pls?
This is the set up for my data. Currently I have graphs, I am using the "slicer" in table3. When I toggle to "Low" on the slicer, it still shows all the data. However, looking at Table3, we can see that "Low" is only related to "Low,Base,High".
Does not make sense, since I do not see how that should bring up my other scenarios.
RelationshipTable 3Table 1- Main TableTable 2- Middle Table
