Community
Select to view content in your preferred language

Improve Messaging for Null/Empty Default Values in Forms

177
3
a week ago
Status: Needs Clarification
RebeccaDempsey
by Esri Contributor
Esri Contributor

Following the latest ArcGIS Update in June 2026, a warning message began appearing in Web Map Forms: 'Default value is not in the list of values. Edit list or update default values in templates'. This message appeared even when the default value configured in templates is valid and exists within the domain list.

A support case was raised and linked to BUG-000186028. As a result, the warning indicator was changed to an information icon, but the message itself remains unchanged and continues to imply that there is a configuration issue.

Through investigation, it appears that the message is triggered by the json value in the source feature layer.

  • When a field is configured with "defaultValue" : "", the form displays: 'Default value is not in the list of values. Edit list or update default values in templates'.

RebeccaDempsey_0-1785158854725.png

  • When a field is configured with "defaultValue" : null, the form displays 'Default values can be set in templates' as expected.

RebeccaDempsey_1-1785158879854.png

 

Although this behaviour may be expected based on the underlying json values (and functionality of the Form is not impacted), from an end user perspective, this may be a point of confusion when the message appears.  Significant time may be spent for the user to review these values in the backend of their data in an attempt to resolve these messages, or review what steps were taken in feature layer configuration for the default values to be "defaultValue" : "" instead of "defaultValue" : null?

Overall, the warning message may be misleading to users when:

  • A user creates a feature layer with a domain list and no set default value at source.
  • Configures a default value in templates for the field (from the list of values in the configured domain).
  • Despite the template being configured correctly, potentially receive the information message suggesting that the default value is invalid or not present in the domain list. Particularly when the message did not appear prior to the June 2026 update.

Improvement Idea
Updating the message to appear as 'Default values can be set in templates' for either "defaultValue" : "" & "defaultValue" : null in Forms may avoid this confusion, prevent unnecessary troubleshooting, and better reflect the configuration of the data within Forms and Templates.

0 Kudos
3 Comments
CraigGillgrass
by Esri Regular Contributor
a week ago
Status changed to: Needs Clarification

@RebeccaDempsey thanks for reporting this; do you have a reproducible case you can share so we can take a look at this and ensure the scenario you're encountering is the one we're considering to improve?  If you do, can share this my public user, "craig_sp" so we can investigate?

RebeccaDempsey
by Esri Contributor
a week ago

Hi @CraigGillgrass ,
 

Thank you for your reply.

 

I have invited your public user, "craig_sp" to a group with test content that reproduces the message I am seeing. From further testing and investigation on this, I have been able to identify the steps to replicate the issue and have outlined these below.

 

From my findings, I think the issue that is causing the difference between "defaultValue" : null & "" may be related to this Bug identified here (BUG-000181790 for ArcGIS Online). I have noted this with support, but as the data's default value remains to be set to None (and if this is expected behaviour), I think the message in Map Viewer Forms could still be improved to reflect the configuration or provide a clearer message.

 

Steps to replicate:

  • Create a new feature layer within ArcGIS Online.
  • Within the feature layer, create a new field. Configure the field with a Default Value of none and a domain list with set values.
  • Review the JSON in the REST URL of the feature layer. Here, the user should see "defaultValue": null for the field added.
  • Create a new Web Map. Add the feature layer to the Web Map, configure Forms & Templates with the relevant field. Here, the user should see the message: 'Default values can be set in templates'.

All the above is expected behaviour. The further steps below are where the issue is introduced and seen in Forms.

  • Go to the feature layer overview page.
  • Export the feature layer as a File Geodatabase.
  • Using the File Geodatabase, publish as a new feature layer.
  • Review the JSON in the REST URL of the feature layer. Here, the user will see "defaultValue" : "" for the field.
  • Create a new Web Map. Add the feature layer to the Web Map, configure Forms & Templates with the relevant field. Here, the user will see the message: 'Default value is not in the list of values. Edit list or update default values in templates'.  
  • With this republished feature layer, adding new fields and configuring with domain lists and default value of None are added as expected with "defaultValue": null in the JSON and no warning message in Forms.
  • Additionally, the user will continue to see Default Value: None in the data overview of their feature layer for fields even with the empty string.

 

Thank you,

Rebecca.

CraigGillgrass
by Esri Regular Contributor
yesterday

@RebeccaDempsey I believe you logged an issue for this ENH-000186639?  Since that is now logged, we'll use that issue to report any updates to this.