Latest Contributions by DamienPyne

Hi We are in the process of uplifting from Pro 2.7 to Pro3.1 and have found contingent values are working differently and changing the selected asset type. We have a large number of contingent values and in many cases have configured the rule to use "<ANY>" for the Asset Type. When we select a new asset to create and populate the value with contingency on it, the asset type is changed based on the first value found in the list where the asset type is not <ANY>. Below is a snip of the rules and example. I selected a new asset of Underground Low Voltage, needing to populate the "nominal voltage", "Phasing" and "number of conductors". When a voltage of 415V is selected, the asset type changes to Overhead service cable low voltage - the first named asset type for 415, ignoring the <ANY> classes. This is not the behaviour in Pro2.7 and although we can manually reset the asset type after populating these fields, is this really the expected bahaviour in pro3.1?

I am trying to consume a service from our ArcGIS Server 10.31 dataset into Pro with our utility network dataset and cannot get the transformation to work. The UNM data is in GDA2020 (EPSG7844), and the older data is web mercator (EPSG3857). This appears to be an incompatibility between AGP 3.1.x to ArcGIS Server 10.31. It is noted that AGS 10.31 is no longer a supported product. It's noted that AGS 10.31 does not support GDA2020 transformation and it has to be done manually through a client application (like AGP 3.1.x). When adding Web Auxilairy sphere services (EPSG 102100, 3857), the 3.1.x AGP client application does not apply the spatial transformation locally for map objects set in GDA2020. The service fails to display geometry. Is this a known issue? Does anyone have an approach to overcome this?

‎08-07-2024

Thanks @RobertKrisher I will pass this information back to the team and get back to you.

‎08-07-2024

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.

‎08-06-2024

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 the find subnetworks tool is now case sensitive. Has anyone else found this? Is this meant to be functioning like this in Pro3.x? Obviously not an issue if the subnetwork names are all lowercase or uppercase and searching is only conducted this way. But where the user creates the name in title case this can be problematic.

‎08-06-2024

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. ArcGIS 3.1.5 Error – text within the error message is not selectable and can’t be copied. ArcGIS 3.1.5 – Trace via Geoprocessing tool. Error message displayed allows text to be selected and copied 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

‎08-04-2024

This would be very beneficial. We needed to develop some custom code to handle this recently when performing this update. It certainly was not very elegant and a tool would be fantastic if we needed to do this ever again.

‎07-24-2024

Thanks @AyanPalit I will go back and reconfirm its only custom products. If there are any OOTB tools I will reach back out.

‎07-22-2024

@AyanPalit have you been able to consider this with the additional workflow information? Essentially whenever a new process starts from a task, GP Tool or extension, the change to commence the function changes the screen focus for the user. Damien

‎07-18-2024

Hi Ayan Our primary workflow with the issue presenting is our integrated design playback function. This takes an XML fragment from a list the user has selected from and creates, modifies or deletes the required content into the version currently being edited by the user. Each object being processed takes the screen focus from the user. Times are dependent on the design size, but can take up to 15minutes, rendering the users machine unusable for this time.

‎07-17-2024

We have a number of different tools that our team use when editing the Utility Network via ArcGIS Pro. The biggest issue encountered is, when running some of the functions that perform different activities, Pro steals the screen focus, meaning the user is constantly interrupted when trying to perform other activities on a second screen. Does anyone know of a setting or approach to allow Pro to continue to run its actions while letting the user use other system applications.

‎06-04-2024

Thanks Scott, we had been working with the PSS team and came up with the same solution about a week ago. Sounds so simple, created so many questions at the time.

‎05-15-2024

Also, another consideration is your Pro/Ent pairing. We have been advised to keep our products aligned as per the release plan: Announcing the 2024 Network Management Release Plan (esri.com) Pro3.1::Ent11.1 Pro3.3::Ent11.3

‎05-15-2024

Hi, Just out of curiosity, what type of workflow would require you to add a Utility Network Device layer multiple times in the map? I do know issues we have seen testing Pro3.2 we had been advised adding the service multiple times can create issues.

‎04-22-2024

Thanks Mike, I have raised a support ticket.

Online Status	Online
Date Last Visited	3 hours ago

My Ideas

Latest Contributions by DamienPyne

Contingent values changes the subtype selected

ArcGIS Pro3.1 transformation issue

Re: Find subnetworks tool is now case sensitive

Re: Trace subnetwork error message globalid cannot be copied

Find subnetworks tool is now case sensitive

Trace subnetwork error message globalid cannot be copied

Re: Modify Asset Group or Asset Type NAME After Deployment

Re: ArcGIS Pro takes the screen focus

Re: ArcGIS Pro takes the screen focus

Re: ArcGIS Pro takes the screen focus

ArcGIS Pro takes the screen focus

Re: object snapping not aligned to grid location

Re: Error ArcGIS Pro 3.3 Terminal Connections Multiple UN Device Layers in Map

Re: Error ArcGIS Pro 3.3 Terminal Connections Multiple UN Device Layers in Map

Re: Modify terminals pane not showing in AGP3.2

Re: ArcGIS Pro takes the screen focus

ArcGIS Pro takes the screen focus

Re: object snapping not aligned to grid location

Re: Dirty area measurement of use

Re: Dirty area measurement of use

APAC Utilities Community of Practice