Field Maps Designer forcing a default value for required fields
Am I going mad, or has ESRI recently changed the behaviour in Field Maps designer to force you to assign default values to domain fields when the underlying feature service field setting doesn't allow NULL values?
I have a field map template that I've been using for over 4 years now, and it have a number of required fields that have been required because they don't accept NULL values. This template has been duplicated on multiple projects and is working fine on mobile devices.
I have gone to make a modification to the template (my first since January 29th, 2025), and cannot save my changes because the template page has a number of required fields that haven't got default values assigned.
This doesn't make sense, because the surveyor needs to input these values, and having them set to required is necessary to prompt them to input the data. Having it already prepopulated is illogical because then they might forget to update that field and wont be prompted in the app.
I was able to save this template in January as it is, but now I cannot. I am also raising a ticket. Will update with progress on that, but if anyone can advise in the meantime, then I'm all ears.
To re-iterate, this only affects fields with a domain/list assign, with the underlying field set to not allow Null Values
It must be the database level, not allowing null values. That setting seems to not be best practice nowadays, it seems to cause problems with field maps designer.
on a field without "Allow Null Values", it works as intended.
