Hey everyone,
Hope you're all having a good week! I've hit a bit of a head-scratcher with ArcGIS Experience Builder (on Enterprise 11.3, specifically), and I'm hoping someone out there has either figured this out or can commiserate with me.
So, here's the deal: I've got a feature service with a field (let's call it 'Popesti') that uses a pretty standard coded value domain (think A, B, C, D, E). All good so far. I'm using the Table widget in my Experience Builder app, with inline editing enabled.
The Annoying Bit: If a record in my table already has a value in the 'Popesti' field (say, it's currently 'D'), I literally cannot set it back to NULL or an empty state through the Experience Builder Table widget's dropdown. It just... doesn't give me the option. I can change it from 'D' to 'A' or 'B', but I can't "un-choose" it completely.
What's Got Me Scratching My Head (and why I don't think it's my fault!):
Database is Cool with Nulls: I've triple-checked in ArcGIS Pro. The 'Popesti' field is set to "Allow Null Values: Yes."
Data Already Has Nulls: My existing data has plenty of features where 'Popesti' is<No value>, so the geodatabase knows how to handle it.
Pro Does It Fine: If I pop over to ArcGIS Pro, I can easily clear out a populated 'Popesti' field and make it null. It just works, even without a "NULL" code in my domain.
EB Says "Edit Me!": Experience Builder's Table widget definitely has editing enabled for this field.
To me, this feels less like a bug that crashes something and more like a UI oversight in the Experience Builder Table widget itself. It's like the dropdown is perfectly happy to show me all my domain values, but forgot to include the "hey, clear this selection" option for nullable fields once a value is picked. It just kind of assumes you always want some value from the list, even if the database is cool with no value.
This is super frustrating because it means users can't fully manage their data directly in the web app for existing features through the table. Sure, the dedicated Edit widget does work for this, but that's a complete workflow killer from a performance perspective – users have to select a feature, then deselect it from the table, select it again in the edit widget, make their change, save, and then go back to the table. If you're doing this for more than one or two records, it becomes incredibly inefficient. Jumping back to Pro to null out a field is equally cumbersome!
So:
Has anyone else run into this specific behavior with the Table widget?
Am I missing a secret setting somewhere to enable a "clear" option for nullable domain fields?
Is this something Esri is aware of or planning to address in a future release?
Any thoughts, workarounds, or just shared commiseration would be awesome. Thanks for lending an ear!
