Page History
Despite no explicit option currently, there are at least 4 3 methods that could help you successfully handle N-way relationships.
...
| Info |
|---|
| For automation (where the literal value is more important), the value expansion can be added to “Yes*” to replace the value name on export since TCD Automate only reads value expansions, if they exist. |
Method 4: Constraints vs Forced Interactions
The last approach leverages the fact that constraints can overwrite forced interactions, and vice versa.
We start with the “base” initial setup.
Then say that Q2=Yes can never be paired with Q1=No.
Lastly, on the Forced Interactions screen, we force the combination of Q2=Yes with Q1=No and accept the warning that informs us that our constraints logic marks that combination as invalid/impossible.
Doing so will result in the Forced Interaction overwriting the model’s constraints logic. We would get one scenario (and only one) in our data table that would include both Q1 = No and Q2 = Yes. And the correct Question 3 value would appear (“Not displayed”) because we forced it.
We still get the coverage of all pairs and eliminate invalid combinations.
...
| . |