June 2026 Update - Default value error when there was none set for list

[HannahBee]

Last week these errors did not show up. Since the recent update, there is a warning in my Field Maps form that says "Default value is not in the list of values. Edit list or update default values in templates." There was no default value set on any of these lists. The fields in question all have values in them so nothing is blank/null. The option on the field does have nulls allowed but I leave "Include "no value" option" unchecked because I won't want any null input.

This layer also has a hosted view based off of it so I can't really investigate changing things without breaking that first. Wondering if others are noticing this and found what made this warning go away.

[EmilyGeo]

Hi @HannahBee, 

I'm sorry you're experiencing this. This is just an alert, so hopefully it is not blocking you from saving the form or collecting data. Are you able to save the form? 

Would you be able to share a link to the map so we can take a quick look? 

[HannahBee]

Fortunately, it is not  preventing from saving but this warning shows up on all of the fields that have a list of more than 3 values.

This map and its forms contain/are part of secured, utility data. I could make a dummy map and form or record more documentation of the settings on the items. Whichever you'd prefer.

[EmilyGeo]

Hi @HannahBee, 

I'm glad to hear you are still able to save forms and collect data. We are looking into this now. 

Do you see default values when you look at the templates window? 

Thanks! Emily

[HannahBee]

Great, thank you. There are no templates as this is a form for a related table. It is just blank when I go to that tab.

[Scott_Sambell]

Every one of our maps we have checked (100+) have been showing this error on and off, but we have been ignoring it because it is not a showstopper and there are so many other bugs to cope with right now. 

Esri made templates for non-spatial layers non editable in Field Maps designer over a year ago.  We lodged a ticket for that when they made the change, but they have shown no interest in putting it back how it was.  We have to edit the templates for all our related record tables in the REST services directory now which adds a few hours a week to our workload.