topic Re: Value doesn't fall within the Domain even though the field is already filled there ? in ArcGIS Pro Questions

Value doesn't fall within the Domain even though the field is already filled there ?

DEAF_PROBERT_68 — Tue, 16 Sep 2025 18:33:54 GMT

Hey all !

I have a question about File Geodatabase. I added a lot of fields first and then when I made a select of a feature. I entred the name of it in an attribute field.

I realized that it will be a lot of work , so I decided to proceed and add Domains for each field and then add a descripton.

The description names were came from a webpage that I put in the descripton.

When there is a new one I need to add , I went back to the Domain again and then add the new description.

Then I went back to the MapView again and selected a new feature and sometimes I get these.

Funny thing is why does it do that even though I scroll down each feature and all of them in the Allowable Equiment is already filled ?

So I googled for a solution to thins and I found this link https://support.esri.com/en-us/knowledge-base/error-failed-to-create-feature-class-name-value-doesn-t-000031397

Do I need to go back and re-selected again to solve the problem ?

I am using ArcGIS Pro 3.3.6 in Citrix and Recreation.gov .

If anyone in here has a similar issue and if it workied in FME let me know.

I will be adding more like this for other campground in a few ranger districts down the road. For now, I am concentrate with one of our ranger district.

Re: Value doesn't fall within the Domain even though the field is already filled there ?

DavidPike — Tue, 16 Sep 2025 19:06:54 GMT

Can you share your Coded Values and Descriptions? It may match your Description but not your Coded Value. Also look out for slight differences or trailing spaces.

Re: Value doesn't fall within the Domain even though the field is already filled there ?

JenniferCadkin — Tue, 16 Sep 2025 19:11:36 GMT

Something that may help you as you track this down...if you are needing to edit the feature's attributes and the error is preventing it, uncheck 'Enforce Attribute Validation' in the Backstage Options, Editing tab. With this option unchecked, there will be warning notification, rather than and error notification, and you will be able to modify the data.

https://pro.arcgis.com/en/pro-app/latest/help/editing/editing-options.htm#ESRI_SECTION1_9E23F817ABB7489C8164469015FC559F

Re: Value doesn't fall within the Domain even though the field is already filled there ?

CalvinHarmin — Wed, 17 Sep 2025 16:19:59 GMT

I find when diagnosing the warnings like you're seeing where domain coded value is not being recognized in a selected feature:

For that layer in your map, if you open the attribute table, there is an option to specifically show domain CODE values instead of DESCRIPTION values. This also changes the behavior of what you see in the attribute pane (but not pop-ups, I believe; you have to change that field value display behavior separately by using an arcade expression to show the domain code value rather than description).

This at least helps you see what the 'actual' value of that field is.

Changing domain description values in the domain menu should automatically reflect the new description value in your attribute table/attribute pane, unless ArcGIS Pro is being glitchy you may want to close and reopen the project.

However, if you change any domain code values, you have to manually update features that need to have that new code value applied.

Re: Value doesn't fall within the Domain even though the field is already filled there ?

DEAF_PROBERT_68 — Wed, 17 Sep 2025 16:22:27 GMT

Thank you , Yes I see glitchy here because it does not refresh very well. I see some issues when you change field in Unque Values and I see duplicate here.

It is like you said you have to close the project and then re-open the project to make the change or glitch disappears.

This morning I opened the project and I don't see anything strange in Unique Values...along with the show count.

Re: Value doesn't fall within the Domain even though the field is already filled there ?

DEAF_PROBERT_68 — Wed, 17 Sep 2025 16:36:14 GMT

I am reviewing again here and found some strange here ....

In that picture you see I have two separate No here.. that is the problem...

Re: Value doesn't fall within the Domain even though the field is already filled there ?

DEAF_PROBERT_68 — Wed, 17 Sep 2025 16:41:42 GMT

For Fields

For Domanis

For Subtypes

Re: Value doesn't fall within the Domain even though the field is already filled there ?

CalvinHarmin — Wed, 17 Sep 2025 16:46:51 GMT

Can you say more about this - I'm not sure what you mean:

I see some issues when you change field in Unque Values and I see duplicate here.

Re: Value doesn't fall within the Domain even though the field is already filled there ?

CalvinHarmin — Wed, 17 Sep 2025 16:52:06 GMT

I think you accidentally pasted the Subtype screenshot twice -- can you paste the domain menu screenshot showing the domain code/values you are having issues with?

Re: Value doesn't fall within the Domain even though the field is already filled there ?

CalvinHarmin — Wed, 17 Sep 2025 17:21:43 GMT

What I can tell from this screenshot is that you have the value "No" as the actual value of some of these features. If I'm following correctly, the actual value should be "1" so that it is a valid domain code value.

What you may have to do is turn off the attribute table option for 'Show domain and subtype descriptions'.

In the attribute table, select all features that have the value 'No'.

Right-click on the Site_Accessible field in the attribute table and click Calculate Field.

Now you can 'force' those values to be "1" through the Calculate Field operation. Ensure the option to 'Use the selected records' looks correct and that you are applying the value to the correct field.

---

Another option is to temporarily remove the domain applied to that field you're having trouble with. That will make it easier to find and update 'actual' values that do not match the code value(s) you need to assign.

After editing all features to have the correct code values, then you could re-assign the domain to that field.

Just a warning that when using a field with domains -- if you use Calculate Field, you must use the code value when applying values with Calculate Field -- if you try to apply a description value with Calculate Field, it does not 'check' if this matches a code value in the domain to assign the code value instead. Calculate Field is more of a 'brute force' edit method. In comparison, the attribute table and attribute pane will show you the drop-down pick list of domain code or description values to choose from and will not let you manually enter a value, even if you wanted to.

This is a big problem in my opinion with ArcGIS Pro and domains, maybe it's a bug: if you have a domain description value as the 'actual' value in a feature with a domain, the attribute pane may display it as the matching code value, even though it literally isn't. It's super confusing.

Re: Value doesn't fall within the Domain even though the field is already filled there ?

DEAF_PROBERT_68 — Wed, 17 Sep 2025 17:20:02 GMT

Look at the picture scroll down here. Look at the Site Accessible and I have two "No"'s and when I fixed it and refresh the count One of the No count changes to zero. It means the No now have only One label...

Example I just fixed Check-In and it does not refresh the Value "1" because I move the clock 2:00PM from Value 1 to 2:00 PM

Re: Value doesn't fall within the Domain even though the field is already filled there ?

DEAF_PROBERT_68 — Wed, 17 Sep 2025 18:11:32 GMT

Got it !!!!!! That is the solution I am looking for !

Tricky !!!

Re: Value doesn't fall within the Domain even though the field is already filled there ?

Town_of_Fuquay-Varina_GIS — Wed, 17 Sep 2025 18:34:36 GMT

edit (sorry can't delete)

Re: Value doesn't fall within the Domain even though the field is already filled there ?

CalvinHarmin — Wed, 17 Sep 2025 18:38:45 GMT

Glad to hear it, and you're not alone with having trouble with with situation of updating mis-matching values to for domains. It can be a pain.

I think ArcGIS Pro could be much more helpful to the user to dynamically show both code and description values in the attribute pane to make sure you are clearly able to see the issue when it finds a value that does not match a domain code. Maybe I can submit this as an idea in the forum if it's not already there.

I recently had to explain to a consultant GIS analyst this same issue when they provided a deliverable where almost all the feature values were 'description' values instead of the codes for the domains that they themselves set up. We had to go back and forth a few times and I had to explain it in a few different ways until it clicked and we got it all corrected.

Re: Value doesn't fall within the Domain even though the field is already filled there ?

DEAF_PROBERT_68 — Wed, 17 Sep 2025 19:58:59 GMT

Thanks for educated me. It opened my eyes now ...