Select to view content in your preferred language

Opening Attribute Table of Dirty Area Layer after Add Join is Crashing Pro

272
2
Jump to solution
04-16-2025 10:16 AM
BrandoCrozier
Occasional Contributor

Hello Team,

We made a layer of Dirty Areas that looked at a specific Error Codes and limited to Electric Device (This ensured a smaller dataset on the new layer). Then we did an add join using Feature GUID. All went well. Then we went to open the Attribute Table and Pro crashed. We tried this on multiple computers and got the same result. Has anyone else seen this happen? 

1 Solution

Accepted Solutions
gis_KIWI4
Frequent Contributor

@BrandoCrozier - I tried replicating the issue but it seemed to work on my version.
Working on enterprise gdb and ArcGIS Pro 3.4, Enterprise 11.3
I created a join on the Dirty Areas Layer the same way you did. 

gis_KIWI4_2-1744835675066.png

I even used the "create a layer from slection" option and was successfully able to add joins. 

Another avenue you could pursue is the "Summarize Utility Network Errors" Tool - This a part of the UDMS toolbox. This should give you more information than the Dirty Areas Table but it won't be "live" and will be a snapshot of the errors.

gis_KIWI4_3-1744836251125.png

Couple of things you could try if you wanted to continue down the path you are currently trying. 

  • The paths when setting up the join are absolute paths rather than mapped directories/one drive
  • If you are working with a fileGDB, try replacing it with mobileGDB
  • If you have access to a different version of ArcPro, give that a go. 


View solution in original post

0 Kudos
2 Replies
gis_KIWI4
Frequent Contributor

@BrandoCrozier - I tried replicating the issue but it seemed to work on my version.
Working on enterprise gdb and ArcGIS Pro 3.4, Enterprise 11.3
I created a join on the Dirty Areas Layer the same way you did. 

gis_KIWI4_2-1744835675066.png

I even used the "create a layer from slection" option and was successfully able to add joins. 

Another avenue you could pursue is the "Summarize Utility Network Errors" Tool - This a part of the UDMS toolbox. This should give you more information than the Dirty Areas Table but it won't be "live" and will be a snapshot of the errors.

gis_KIWI4_3-1744836251125.png

Couple of things you could try if you wanted to continue down the path you are currently trying. 

  • The paths when setting up the join are absolute paths rather than mapped directories/one drive
  • If you are working with a fileGDB, try replacing it with mobileGDB
  • If you have access to a different version of ArcPro, give that a go. 


0 Kudos
RobertKrisher
Esri Regular Contributor

@BrandoCrozier  If you can consistently reproduce the crash, please create a case with support.

The approach outlined by @gis_KIWI4 to use the Summarize UN Errors tool is the recommended approach.