Default value for multiple choice fields not working.

[RickSteekelenburg]

The new multiple choice field doesn't register a default value even when it was set when adding the field directly to the feature layer instead of the template.

It shows in the form but it doesn't do anything.

[MErikReedAugusta]

By chance, do you have subtypes enabled on that feature class?  I haven't worked with the multiple choice fields, yet, but this problem catches me napping every once in a while when I'm doing schema updates on a feature class with subtypes.  I'll set the default value on the Fields view, without remembering that the Subtypes view has a completely separate default value, which is the one that actually matters.

[Megan-Hendrick]

Hi Rick, 

One thing I would check is that the default value you are using matches the code of your multiple choice element. For example: If I wanted a default value of Steel Toes Boots and Safety Vest to be reflected in this multiple choice element (see screenshot below), I would set the default value to "boots,vest". Note that you need the comma delimiter (without a space), to match the case sensitivity, and to match the code not the label. 

Let me know if you are still having issues!

[RickSteekelenburg · Accepted solution]

Nevermind, it's been a long day.
I was editing an existing feature instead of adding a new one and wondering why it didn't show.

Thank you for your time.