While in field view I turn off/on certain fields, however when I go to save this change it doesn't let me.
Then when I try to exit from the field view tab I see this.
Is there another way to turn off and on field visibility?
Drew, do you have any active feature edits that are not saved under the map view?
If there are outstanding unsaved edits under the map view then Pro wont let you make changes to the attribute table under the table view.
What version of ArcGIS Pro are you using? Also, what type of layer are you working with (i.e. enterprise geodatabase feature class, shapefile, feature service)?
I'm working with ArcPro 2.0.0, working on a polygon layer within a file gdb
Is this reproducible on other feature classes in the same File Geodatabase? In a different File Geodatabase? In a new ArcGIS Pro Project?
Yes, it happens on every layer in my FGDB (including different geometry types). I have not tried with another FGDB however
Somewhat strange... but here is the scoop
Toggle the field off.. unchecking Read Only if necessary.
Save your edits otherwise you get the warning
Close the table
Open the table and the field should be hidden.
Otherwise, just right-click on the field name, and 'hide' field. this isn't permanent and the field will reappear when reopened.
The issue for me is that I am unable to save after making any changes, but the popup warning confirms that changes have been made, despite the save button being greyed out
I would try another File Geodatabase to see if it's something specific with this geodatabase. Also, 2.0.1 is available for ArcGIS Pro. I would recommend upgrading to that version by clicking Project > About.
Forgot to mention... I was using 2.0.1....
Thank you Mervyn, that solved my problem.
My add-in updated the table of attributes but did not save afterwards, preventing me from saving my changes to the tableview.
outstanding edits saved > still unable to save new fields added...
check/uncheck visible a fix for me...
yup... a pop-up or something more intuitive/instructional than greyed out would greatly assist UX.
Ridiculous how steep this 'migrate prod env to pro' curve is proving...
hoping the long term efficiency gains are worth the short term pains and inefficiencies
A pop-up stating that there are unsaved changes pending before the "edit field" interface even comes up would easily solve this problem. Having a button greyed out with no indication as to why is very frustrating and isnt the most intuitive from a UI design perspective.
If you hover over the save field changes icon, a banner comes up stating that there are unsaved feature edits. You're right though, this is not at all intuitive and took me awhile to figure out.
Thanks - I had that question too!
Retrieving data ...