Test for resultValue or resultValueX
To ‘X’ or not to ‘X’, that is the question:
Whether ’tis nobler testing ‘text’ with resultValueX
To check against the description of an item in a list
Or, with resultValue, check just the id
And, if it changes, still obtain the required result?
Actually, there is no need for drama …
… resultValueX tests against the text of a result and resultValue tests against the id of the result.
To give a bit of context …
Both of these tests are used primarily in Display Conditions. Display Conditions are used on template items to show or hide a question depending on what has been entered previously.
For example, if a list includes an ‘other’ option which requires additional text entry, it may be undesirable to make a permanent text box. A test can be added to the text box so that it is only displayed if ‘other’ is selected from the list.
This blog discusses whether to test against the text (‘other’) or whether to find the id of the list item (from the List Items menu item) and test against that.
|Use resultValueX (or rVX) if the text is static
|Use resultValue (or rV) if your text is long or might change whilst maintaining the same basic meaning
This also applies to other conditional places in magic5 where resultValue is applicable.
For further information, see
If you are using the new magic5 UI, your list item id will appear something like this …