ArcGIS Pro 2.3 Bug

[MarcosMendez]

It appears I cant edit some fields after installing the 2.3 update. On some fields, I'll get an error saying that I cant edit the field because it is not part of a domain, even though the particular field has no domain values assigned to it. I've been having the same issue on multiple computers and 2 different Pro accounts, as I work for 2 organizations.

[MichaelVolz]

How do you get a value that does not fall in the domain?  Was this a legacy value from before the field was defined by a domain?

[ThomasColson]

Having values that are not part of a legal domain value is a pretty common occurrence, especially "databaseizing" legacy data, which makes this bug that much more of a major issue. Example, let's say I take an old shapefile of fish tissue sample locations (for genetics testing), and one of the fields is "StreamName", I import all that into a SDE GDB, apply a domain to "StreamName", BUT, I use the NHD GNIS Names as the source for this domain (we don't want folks picking Sasquatch Creek 'cuz, sadly, it doesn't exist). However, some joker listed half the sample sites as being on Sasquatch Creek (they're really on Big Foot Prong) in the shapefile, so now, in my GDB, when I edit this record, the error throws. However, in Pro 2.4, it throws a red warning but lets you commit the edit. 

[AmandaRoss]

Exactly, it was a legacy value. Glad to know 2.4 allows you to edit those rows anyway! That's good news.

[MichaelVolz]

Is there a tool out there that would make it easier to find values in a field that do not fit within the currently defined domain?

[brianvan_druten]

I am running into this same issue in Pro 2.3.3.  We have a database created in Survey 123 for field data collection of banded birds.  Since its original publication earlier in the season, we have added new band combinations in Survey 123 and republished.  Those do not show up in the domains that Pro 'sees' (another issue in itself).  So for any of these new band sightings that were collected in the field, it will not let me edit any of the other data associated with that record, even if I am trying to change something from the original picklist in another column.  I am able to edit the data if what was in the original publication of the database from Survey 123 is what the field user selected.