Latest Contributions by JonDeRose

‎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.

‎03-23-2021

Good morning Rudy, While the utility network is not industry specific, we do have a Learn lesson that allows users to explore the components of the utility network through the lens of an electric configuration. Get Started with the ArcGIS Utility Network This lesson was originally authored for the ArcGIS Pro 2.5 release and has recently been updated for 2.7. Take a look and let us know what you think. Thanks, Jon

‎03-22-2021

Good morning Curt, I am sorry to hear of the frustration caused by this issue. From the description it sounds as though you are encountering an issue (BUG-000138339) we have addressed in the 2.8 release. As you noted, this is caused due to the omission of a Path Direction when the Trace tool is launched from the Tools gallery with a Shortest Path trace. This behavior is only encountered when launching the trace from the Tools gallery and should not be encountered when opening the Trace tool from the Geoprocessing pane and choosing the Shortest Path trace type, or if a Path Direction is specified after launching the tool. - Jon

‎03-15-2021

@Thom_Leeffers Just to clarify, you should not need to unversion your data or "flatten your versioning tree" to make schema changes, add rules, etc. While removing existing named versions to add rules, etc. may be completed as a best practice to prevent the need for additional steps to be performed with each existing version...it is not required. The schema of the data itself is not versioned, and (as an example) any rules that are added to the Default version would be pulled into the named version through a reconcile. Here's a KB in ref to versioning of table schema (older but remains relevant with branch): https://support.esri.com/en/technical-article/000008159 We will investigate methods to clarify this further in our documentation. Here is a doc reference regarding rule modifications wrt deletion: https://pro.arcgis.com/en/pro-app/latest/help/data/utility-network/delete-a-connectivity-or-association-rule.htm - Jon

‎03-11-2021

Hi @Thom_Leeffers Many utility network configuration steps require working against a utility network with a disabled network topology (Add Rules, Add Network Attribute, etc.); however, unregistering data as branch versioned is not required. The only operation that I can recall that ONLY works against a non-versioned dataset is Enable Network Topology (when using the Only generate errors option). I'll see about getting a note added to clarify this exception. In other cases, the "Versioned Data Required" column in the topic you referenced simply indicates whether it must be versioned or not. There are many examples that will work regardless of the versioning status (i.e. No), while others require the data to be registered (i.e. Yes). The reason for this is that many configuration steps may take place before registering your dataset as versioned. - Jon

‎03-08-2021

Seconding Dan's suggestion. The script is "correct" as written however, the issue is most likely access to the data.

‎02-23-2021

@TJ_Houle This issue is encountered if you right-click the feature dataset containing the utility network to add it to the map. Sorry for the inconvenience, we have addressed this with the upcoming Pro 2.8 release. The issue should not be encountered if you right-click the utility network itself and add this to a map. Thanks, Jon

Online Status	Offline
Date Last Visited	2 weeks ago

My Ideas

Latest Contributions by JonDeRose

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: Add Electric Focused Lessons to Learn.ArcGIS.Com - Status changed to: Implemented

Re: Trace Network Shortest path errors with 999999

Re: Modifying Component in Utility Network with Branch Versioned data

Re: Modifying Component in Utility Network with Branch Versioned data

Re: Export features from Dirty Area layer using Python (ArcGIS pro 2.6)

Re: Duplicate UNs Added to Map

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

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

Re: Display Flow Direction in Trace Network servic...

Re: Display Flow Direction in Trace Network servic...

Re: Problems with Published Trace Network Service