I loaded a point feature layer with 178 records in arcgis pro 2.5. Everything is showing in the map as expected. But my attribute table is not showing:
the switch button switches the selected rows but shows nothing. The Fields View button results in
Other layers in the map are showing their attribute tables ok.
the layer shows up OK in arcmap 10.6 and the attribute table is visible also in 10.6.
I downloaded the layer as gdb from agol. I have done this before and had no problems earlier.
thanks for your time,
Bert
Solved! Go to Solution.
Same issue here. The data is there, as pop-ups will work, but I can't do anything with the attribute table itself.
Same behavior for me as well. I was able to use Xtools to view the attribute table in Excel too.
Hi,
I also have a HFL that is not showing attribute tables for 2 layers in ArcPro 2.5 but fine in arcmap and arcgis online. The other 7 layers in the HFL show the attribute table fine in ArcPro and elsewhere as well.
Has anyone been able to resolve this issue yet with ESRI technical support?
Andrew
I also have had the attribute table not display in ArcPro from a downloaded file geodatabase of a feature service hosted online. Check the editor tracking date fields in the Arc Catalog field property window. I had a default date of 12-31-1899. Removed the default value and I can now see the attribute table in ArcPRO. Republished the service with overwrite web service and things seem to back on track. I do not know how I accomplished getting the default values set in the tracking fields. But I am glad to see the attribute table is back. I hope this helps you.
John.
Glad you got it working, but this was not the solution for me. Still grasping at straws.
I'm having the same issue. Here are the steps that I take to recreate the issue and what I've done to try and troubleshoot it...
My only workaround at this point to be able to access this data in a 'working' fgdb in ArcGIS Pro is to use a third party tool (Enterprise Architect) to rebuild the fgdb for me. The steps I take to do this are:
So, it looks like I'm going to submit a support ticket with Esri to see if they can figure out why certain fgdb's experience this behavior. Based on the above, the only odd thing in my feature service are some weird default values (-2209161600000 Update - this shouldn't really be an issue since this is really just 12/30/1899) for date fields that I'm not sure how they got there. These aren't default values for the Editor Tracking date fields, but for other date fields. When I inspect fields via python or ArcCatalog, I don't see these default values. They also don't show up in the XML as default values, it only shows up in the GDB_ServiceItems table in the xs:string for each Record in the fgdb.
UPDATE 6/22/2020: Thanks to Bert Kraan, I pinpointed my issue to the default values for those date fields. For some reason these default values cause issues in ArcGIS Pro and it hasn't been addressed yet in 2.5.0 or 2.5.1. If this happens to someone else, I've got two workarounds.
Once I did either of the workarounds, I was able to view the attribute tables in ArcGIS Pro.
UPDATE 6/23/2020: Esri support has confirmed for me the existence of BUG-000126591 - "Unable to view the attribute table after exporting the hosted feature service as a file geodatabase consisting of a date field." The bug is currently in the product plan and seems to effect ArcGIS Pro versions 2.4.2 to 2.5.1. Another workaround that support mentioned was exporting to shapefile, but that doesn't work for me due to relationships and long field names.
Support told me the default value for the datefield (12/30/1899) is exactly what triggers the bug (their words). It should be fixed by now, in the end I worked around by using arcmap 10.6 which works fine with my dataset.
Thanks Bert. You're right. I did some additional testing and this appears to be the culprit, but it is not fixed in 2.5.1. I'll see what Esri support says.
I was so happy to find this question since I've been struggling with the same bug. I cleaned my date values and even deleted the old creator date fields and only left one date field that doesn't have any null values. And it still won't show up in Pro 2.5.2! is there any news on this lately?