Improve Messaging for Null/Empty Default Values in Forms
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'.
- When a field is configured with "defaultValue" : null, the form displays 'Default values can be set in templates' as expected.
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.
