Latest Contributions by JonDeRose

‎06-29-2021

Emerson, Is this a reproducible from a backup? From the error it appears as though the upgrade is attempting to add the SUPPORTEDSUBNETWORKNAME field as a non-nullable field; however I am not sure why that would be the case. When upgrading a UN from v3 to v4 this field would be added to classes as a nullable field. How does this UN dataset differ from the other two that succeed? What is more concerning is the reference you made about the upgrade process unregistering your data as versioned. It would be interesting to investigate this further. I found the support case you referenced. If this remains reproducible I recommend that you work with the analyst through that case to provide the backup and reproducible case for analysis. Jon

‎06-25-2021

@NickHarvey I'm glad that Alex was able to provide you with the solution. This also highlighted an oversight in the documentation that should have been updated with the ArcGIS Pro 2.8 release. We've made the change for the next release. While the note still holds true when tracing through loops without directional devices, the updated note should read: "When loops are encountered during an upstream or downstream trace, trace results will return all features in a loop unless devices with a directional terminal configuration are present."

‎06-17-2021

@DavidDamian I am not able to reproduce the issue you reference in testing on Pro 2.7 or more recent releases. If the issue persists please reach out to Esri Support to investigate this issue. - Jon

‎06-16-2021

There are no plans for future development in ArcMap. It is possible to edit a Trace Network in ArcGIS Pro while projected on the fly, however. The trace network shares a common framework with the utility network but was designed with existing nonutility users of the geometric network in mind. Existing geometric networks can be easily converted into a trace network starting with ArcGIS Pro 2.6.

‎06-08-2021

Which Pro version are you using when this is encountered and are there any additional details reported in the server manager logs or via Fiddler when the issue is encountered? The error itself points to an issue with a recent geometry update, are any similar issues encountered with Validate? Jon

‎06-03-2021

@RobertThomson Using the data you provided I was able to reproduce and confirm that we've addressed this issue in the upcoming 2.9 release. I've exported this as BUG-000140438: Create Trace Network fails with Error 160084: "Cannot create a dirty area outside the topology's spatial domain." Jon

‎05-17-2021

@JamalNUMAN I would recommend creating a case with Support to review and determine if the issue you are encountering is reproducible and related to the defect you referenced or something else that the team needs to investigate.

‎04-30-2021

The sample workbench file outlined in the blog series: "Leveraging Data for External Systems - Automating Export Subnetwork using Data Interoperability" can be found below. Leveraging Data for External Systems - Automating Export Subnetwork using Data Interoperability https://www.esri.com/arcgis-blog/products/utility-network/data-management/exporting-subnetworks-using-data-interoperability/ Leveraging Data for External Systems - Automating Export Subnetwork using Data Interoperability - Part Two https://www.esri.com/arcgis-blog/products/utility-network/data-management/exporting-subnetworks-using-data-interoperability-part2/ @RenatoSalvaleon

‎04-12-2021

Good morning @LorenMueller Great question! There should not be any issues encountered using a later ArcGIS Pro client (such as 2.7) to interact and work with an earlier version of the utility network (such as UN v3). To put it another way, while you can use a newer client and server version to take advantage of new functionality, there is no obligation to upgrade the utility network's version to be "current" with the client or server release. While some capabilities and functionality may only be available with later versions of the utility network (such as working with nonspatial objects), this does not prevent the client from working with the earlier version. The compatibility chart you referenced is primarily concerned with the version of the utility network created through the combination of client and enterprise during creation or upgrade. The version of ArcGIS Pro and ArcGIS Enterprise determines the Utility Network Version value when creating or upgrading a utility network. Earlier ArcGIS Pro releases cannot open utility network datasets that participate in newer functionality. For example, you'd encounter issues if you tried to use ArcGIS Pro 2.4 and ArcGIS Enterprise 10.6.1 for sharing a utility network that has a Utility Network Version value of 4. Hope this helps to clarify. - Jon

‎04-12-2021

Hi there @OskarasAlšauskas Is your goal to test out the ArcGIS Utility Network itself? If exercising the utility network functionality, this can be done without the need of a ArcGIS Utility Network user type extension as long as you are using ArcGIS Pro at the Standard and Advanced license level. A single-user deployment of the utility network in a file geodatabase will enable you to leverage all of the utility network functionality available within an enterprise deployment without the need for a additional user-type extension license (with the exception of publishing and working with services).

‎04-02-2021

@GIS_Solutions Just to add to what Dan said, while traditional versioning is not supported by some datasets (such as the utility networks and parcel fabrics), this does not prevent you from using both to support your workflows. You can use branch for the utility network while also registering data that is not part of the network using traditional versioning to edit in ArcGIS Pro via database connection. This topic provides some additional information into management strategies such as this: https://pro.arcgis.com/en/pro-app/latest/help/data/geodatabases/overview/data-management-strategies.htm

‎03-29-2021

Thank you for the reply @GIS_Solutions I understand this should not be seen when working with branch versioning but thought there might have been issues related to a previous cached connection that might not have been configured as branch initially. I can force the error if I intentionally attempt to register as traditionally versioned with move to base before changing he connection properties, otherwise I cannot replicate. If you are able to reproduce this issue with a new database connection in a new instance of Pro and provide the steps you are using to reproduce the issue I would be happy to review this further on my end. Just a note on labels. We are looking into ways to improve the experience with them in this community; however, please know that these are not required to create a new post/question. If you hover over the info icon this provides more detail and communicates that these labels are optional. Thanks, Jon

‎03-29-2021

@GIS_SolutionsI've moved this post out of Ideas into Questions. The error message you are receiving is consistent with registering a feature dataset containing a UN without using a branch versioned database connection as @JayantaPoddar noted. When registering the dataset containing the UN as versioned At any point did you see this dialog, and if so, do you select the check box and click OK (Note: this option is not supported for datasets like the UN)? Can you confirm the Geodatabase Connection Properties for this particular database connection are now set to Branch as shown below? On the other dataset that you are able to register as versioned, can you confirm it is registered as branch? (Right-click feature class and open Properties, view "Versioning". Does this read "Branch"? If yes to all of the above, does the issue persist after closing and restarting ArcGIS Pro? It is possible you are running into a workflow related issue caused by an initial caching of the register as versioned using move-to-base. In testing I ran into a similar issues but was able to get past this by closing and re-starting Pro. I am going to look into this issue further. Jon

‎03-24-2021

‎03-24-2021

Thanks @curtvprice To confirm, this is seen when you are attempting to place a new starting point in the trace locations pane? Is there any change in behavior depending upon the network feature you place the starting point on? Does the feature display in the the pane pane before it is displayed on the map? Working with a large NHD sample dataset I am not able to reproduce similar behavior but I'd like to get a better idea of what you are encountering. Could you share the diagnostic log from the ArcGIS Diagnostic Monitor while performing the action? Open ArcMon by pressing Cntrl + Alt +M, enable Diagnostic log (logs to C:\Users\<user>\Documents\ArcGIS\Diagnostics\ArcGISProLog.xml) and attempt to place the starting point.

Online Status	Offline
Date Last Visited	3 weeks ago

My Ideas

Latest Contributions by JonDeRose

Re: Upgrade UN Failure

Re: Trace results with loops and double-outlet sewer structures

Re: How to report a bug in ArcGIS Pro

Re: Add the ability to edit geometric networks projected on-the-fly - Status changed to: Closed

Re: "Unable to update area or length field..." - Cannot Disable Network Topology

Re: Creating a Trace Network-160310: The spatial references do not match

Re: ArcGIS Pro 2.7.2: Deleting a feature from “utility networks” gets the Pro to crash,

Sample Workbench file - Leveraging Data for External Systems - Automating Export Subnetwork using Data Interoperability

Re: UN versions and Pro - creating vs using

Re: ArcGIS Pro trial for Utility Networks

Re: How can I Register Dataset ? (Error 002764)

Re: How can I Register Dataset ? (Error 002764)

Re: How can I Register Dataset ? (Error 002764)

Re: Improve Trace Network tool parameter validation in ModelBuilder - Status changed to: Under Consideration

Re: Enter points on trace network flow is very slow

Re: Apply Asset Package on UnTools/Pro 3.3 require...

Re: junction-edge from/to connectivity and relati...

Re: Error ArcGIS Pro 3.3 Terminal Connections Mult...

Re: Publishing a File Geodatabase based Utility Ne...

Re: Is it manageable to make something like Up&Dow...