Select to view content in your preferred language

Trace subnetwork error message globalid cannot be copied

100
2
Jump to solution
Tuesday
DamienPyne
Occasional Contributor

We are in the process of migrating from Ent10.8.1, Pro2.7.4, UN3, to Ent 11.1, Pro3.1.5, UN6 and our testers have found this issue where they cannot copy from the error message.

I appreciate this may be due to standard messaging now being used.  Is there a workaround that can be used, outside using the trace/update subnetwork GP tool.

During ArcGIS 3.1 testing that when using the Trace function from the Find Subnetworks tool, the user is no longer able to copy the text from the error message if a Dirty Area is found as you currently can in 2.7.4. 

When performing a trace from the Find Subnetworks tool, ArcGIS displays an error message when a Dirty Area is discovered during a trace.  It displays the Feature Class as well as the globalid for the object associated with the Dirty Area.  Currently in 2.7.4, the user can copy this globalid from the error message and paste that into the OOTB Select By Attributes tool to find the area to Validate (or possibly fix).  Globalids are 36 characters long so manually entering them into a search tool is not an efficient method and prone to entering the wrong characters (and while the error message is displayed, the user can’t use any other tools anyway).

In 3.1, the error message is now displayed differently and the text can not be copied.  This means the user has to manually enter the globalid of the object into a search tool to find the Dirty Area.  The other option is to re-run the same trace in the Geoprocessing Trace tool which displays the error differently and the user can copy the text from that message to use. 

Users prefer the Find Subnetworks trace functionality as it is much faster than the Geoprocessing Trace tool.

----------------------------------------

ArcGIS 2.7.4 Error – globalid is selected and available to copy.

DamienPyne_0-1722999699823.png

ArcGIS 3.1.5 Error – text within the error message is not selectable and can’t be copied.

DamienPyne_1-1722999699825.png

ArcGIS 3.1.5 – Trace via Geoprocessing tool.  Error message displayed allows text to be selected and copied

DamienPyne_2-1722999699831.png

ArcGIS 3.1.5 – No company Config, data added as Subtype Group Layer and Utility Network added through Portal.  Same type of Error message – can’t select the text

DamienPyne_3-1722999699837.png

 

0 Kudos
1 Solution

Accepted Solutions
RobertKrisher
Esri Regular Contributor

UPDATE: At 3.1 a change was made to this dialog, so the text was no longer selectable. You can still select the dialog and press Control + C to copy the text from the entire dialog. Then you can paste it into a notepad to get the message.

---------------------------
Trace Subnetwork
---------------------------
ERROR: One or more dirty areas were discovered. [[ElectricDistributionDevice: {01E0EA22-DA29-4244-98F8-FCBF7BF5DB47}, {9CC09E08-4726-4DE1-A8EC-D5F5A68C5007}]]
---------------------------
_OK
---------------------------

 

There was a change made at 3.1 that caused this text to not be selectable. I have confirmed that this was fixed with 3.3.

RobertKrisher_0-1723041961272.png

 

View solution in original post

0 Kudos
2 Replies
RobertKrisher
Esri Regular Contributor

UPDATE: At 3.1 a change was made to this dialog, so the text was no longer selectable. You can still select the dialog and press Control + C to copy the text from the entire dialog. Then you can paste it into a notepad to get the message.

---------------------------
Trace Subnetwork
---------------------------
ERROR: One or more dirty areas were discovered. [[ElectricDistributionDevice: {01E0EA22-DA29-4244-98F8-FCBF7BF5DB47}, {9CC09E08-4726-4DE1-A8EC-D5F5A68C5007}]]
---------------------------
_OK
---------------------------

 

There was a change made at 3.1 that caused this text to not be selectable. I have confirmed that this was fixed with 3.3.

RobertKrisher_0-1723041961272.png

 

0 Kudos
DamienPyne
Occasional Contributor

Thanks @RobertKrisher.  I will discuss with the team.  With our upgrade project we have been advised to keep the pro and enterprise version aligned.  This means we need to remain on pro 3.1.x.

0 Kudos