Mandatory SC multiple choice variable but *without* a default value?

[JP-ODU]

In SC items, It seems to me that making a Multiple Choice variable mandatory will in turn make entering a default value mandatory. But we don't want that. The idea is the variable should be required and the customer should have to think about it and make a selection. Offering a default value allows them to breeze past the variable and hit submit. We want it mandatory, but blank by default.

Even adding a question choice like blank, N/A, please choose, etc. still counts as an answer for the mandatory variable, and thus invalidates making it mandatory, as a user could just leave it as that option, whereas we want them to pick a "real" one.

I can't seem to find a UI policy that controls this... does anyone know how to fix it?

[Alberto Consonn · Accepted solution]

Hi,

you can easily check the flag Do not select the first choice when you create the Multiple Choice variable, in this way the Default value mandatory check will disappear and you will be able to see the variable without a default value inserted:

If I have answered your question, please mark my response as correct and/or helpful.

Thank you very much

Cheers
Alberto

[Tyler Herman]

Hello,

Multiple Choice variables have a couple type specifications you can use to manage this: "Include none" and "Do not select the first choice". I've included a screenshot below of these two options. Below that screenshot is a screenshot of the actual multiple choice variable on the portal.