ArcGIS Pro 3.3.2 Attribute Tables Gray Out

[DonnaMoreau]

Hello,

This issue appeared in version 3.3.1 also, but it seems to happen more frequently in version 3.3.2.

Scenario:

I selected multiple rows of data in a feature class called Wastewater Gravity Mains. I zoomed in and out of the map a couple of times, then switched the Attribute Table (not window) view to Selected records. It's like the table froze, and icons at the bottom of the table grayed out so that they could not be selected. Sometimes, the records in the table even empty out completely, even though they are still selected in the map.

My solution has been to close out of the Pro session, and when I open it again, everything is fine. However, sometimes that does not work, and then I have to remove the table completely and readd it.

Is there something I am doing incorrectly or could this be a bug in the system?

Thank you,

Donna

[MichaelVolz]

Is there anything special about this data set compared to other data sets where you do not see the issue (e.g. maybe it is part of a utility network)?

[DonnaMoreau]

Hello,

It is not part of a utility network. It randomly happens to different tables in our SDE. Others in my office have experienced the same issue with different feature classes. I've been wanting to ask this question for a while now, and today, when it froze on the wastewater one, I used it as an example. 

Thank you,

Donna

[GSala]

Hello 

I'm encountering a simular issue with my attribute table while I'm editing. The shapefile or feature class tables become uneditable when a record is selected. For example, with two tables open, after selecting a feature on the map, the corresponding row in the table becomes locked and cannot be edited. However, if I switch to another table and then return to the original table, the previously selected row becomes editable again.

I'm facing this problem after I downloaded the 3.3.2 Arcgis pro version

[AmberMillison]

I am experiencing the same thing in 3.3.2 - table is grayed out intermittently when either calculating a field or editing. Same as @GSala , I can usually fix this by clicking another table then clicking back, but this is still frustrating and never was an issue on my previous versions of the software (3.1 and 3.2).

[JesseCloutier]

Hi @DonnaMoreau, we appreciate you sharing a potential bug with the broader Esri Community; however, Esri does not actively track software defects posted here. The official channel for investigating and validating bugs is Esri Technical Support. All customers experiencing a potential software bug should leverage technical support to report and investigate the issue.

By reporting bugs through technical support, Esri can better track the scope and impact of the issue across all our customers and better prioritize it with our product teams. Our teams can also investigate the issue more thoroughly to see if there is a solution, workaround, or patch to get you back up and running as soon as possible.

As a reminder, Esri Community is primarily a self-service support platform where Esri users can ask or answer each other’s questions, share feature requests, and collaborate to solve problems with GIS.

*Note that this is a scripted message prompted when posts allude to a potential product bug.

[DonnaMoreau]

Thank you for informing me of this Jesse!