Value doesn't fall within the Domain even though the field is already filled there ?
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-...
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.
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.
