Always false answers for a true/false datafield

There are some use cases where you want to avoid that the user makes a “wrong” choice. This could be done by making an option “always false” based on certain conditions (previous answers). However, that does not seem possible at the moment, if I’m not mistaken. That said, there is a work-around to obtain kind of the same result.

That work-around could be to use two different change-sets to change the datafield, and don’t show the question (or delete it), but this is a bit less transparent for the user, unless you combine it with showing a certain comment. And, in my experience, using change-sets for this purpose makes the maintenance of the Q&A a bit more difficult (as you have to remember that there was a change-set for this purpose, or you have to be very explicit when you name both change-sets).

That said, this work-around is only possible for true/false datafields and is less of an option to exclude certain predefines for a list datafield (well, it may be technically possible but that would make it rather complicated, I think).

I just want to make sure that I did not overlook the possibility to make an answer option “always false” based on a condition.

Another work-around could be to make the question invisible, tie it to a switch condition, and show a comment to the user. But it is actually not a real work-around as it is not possible to block the visibility of a question and still enable the linked datafield. If you do not show the question, the datafield is ignored (which makes sense).

(We had an oral discussion about this topic, but for the future reader it may be interesting to read about a few nuggets we discussed:)

  • There is a question option that allows you to show disables predefines, so that they will not be hidden.


  • We will probably add a feature in the future to also allow the author to disable a “true” or a “false” (depending on conditions being met) in a true/false question.

  • The current dataflow is typically “end-user selects option, and that value gets stored in a datafield”. Using that and other values, you can then build conditions. There are only a few situations where you can cause a question to also store data in another datafield. One option is to use spreadbases, another is to use change-sets for datafields.

1 Like