Latest Contributions by MelissaJarman

‎11-09-2020

Thanks Jamal - Getting more information about how the data got in this state would help us pin point the issue. You also cannot generate network diagrams with the network features in the current state. After you make a slight edit to the feature to generate a dirty area, validate works, and then a connected trace can be completed. Interested in hearing more about the order of operations to see if this can be replicated.

‎09-09-2020

Thanks for the additional information John! This helps to understand your workflows and it is just a simple preference that users not directly edit default. You do trust these same users to post to default, but would also prefer to add additional requirements prior to post such as validation. We currently have validation attribute rules that can be evaluated via services, but there is currently not a way to force validation to be run before posting. Until a solution like this is available out of the box.... You could use the ArcGIS Pro SDK to remove the default Post button and replace it with custom code the runs validation first.

‎09-08-2020

Thanks for your feedback. With the release of 10.8.1 there is a new portal privilege that will allow you to create custom roles for users that need to serve as version administrators for services with the Version Management capability. This will allow you to grant permissions to perform these version administration tasks for branch versioned datasets via services without having to be the service owner or having to be an administrator. Under Version Management, you can read about the Manage all privilege. User types, roles, and privileges—Portal for ArcGIS | Documentation for ArcGIS Enterprise Currently, this portal privilege is an all-encompassing privilege that is not separated into individual tasks: Your comment about being able to post to a protected default while not being able to directly edit the protected default version is interesting. This is a request we have heard from others users as well in discussion. Please feel free to elaborate on what workflow this would help facilitate.

‎07-28-2020

You will still be able to perform schema modifications when connected directly to the database connection. This will be performed as the data owner, just as you would for any other registration type.

‎07-28-2020

For the first image you posted - I would recommend we retest with the final version of ArcGIS Pro 2.6. There were some issues addressed after beta 3 with incorrect error messages being returned. To answer your question: You shouldn't have to account for junctions that will always be between edge features by including them in both types of rules.

‎07-23-2020

Here is the Geonet Idea: https://community.esri.com/ideas/18569

‎07-23-2020

I agree with Anthony - perhaps the error string is a bit misleading as it uses 'junction-edge' in the wording. When creating Junction-edge and Edge-junction-edge rules you need to review the relationship of junction features relative to the edge features. Junctions that are located at the end of an edge feature need to be included in junction-edge rules, and junctions that are located between edge features need to be included in edge-junction-edge rules. When both rule types are present, junction-edge rules are honored before edge-junction-edge rules.

‎07-20-2020

We have an existing issue we have logged regarding duplicate line errors for connectivity when the asset group and asset type do not match and there are no supporting rules. This is only going to be reproducible for Utility Network Version 3 and older. With ArcGIS Pro 2.6, utility networks will be created and upgraded to Utility Network Version 4. Utility Network Version 4 started using a new error model where the network features themselves are flagged as errors and there are no longer point, line, and polygon error features. Both errors are cleaned up after you fix the error situation and validate I assume? Do you only experience duplicate error features for certain types of errors? Error feature management—ArcGIS Pro | Documentation

‎07-16-2020

Our teams worked hard to add support for branch versioned topology this release. This work was done by the geodatabase and feature service teams to support a new topology layer for web feature layers and enabling many of the validation workflows through the gp tool and error inspector via services. We currently don't have near term plans for implementing branch versioning for network datasets. Here is a new blog with some highlights of new geodatabase functionality for 2.6/10.8.1 - What's New in the Geodatabase at ArcGIS Pro 2.6

‎05-18-2020

This topic would be a good form of reference for you - Utility network management tasks The UN has an additive model for domains and subtypes. If you need to make changes to existing subtypes or domains that are being used on the ASSETGROUP and ASSETTYPE fields for network classes you will have to use the Utility Network Package Tools to create asset packages and start fresh with a new UN. Utility Network Package Tools | ArcGIS Solutions Very similar to this bug as well. BUG-000115603: When trying to remove a subtype from a feature class..

‎05-18-2020

I am not sure what the cause of the error you encountered was, but don't think it was because the UN was not versioned. What you are seeing for the feature layer properties .... I think it has to do with the UN layer itself being a group layer... If you look at the sub layers of the UN (Dirty Areas), you'll see that these are versioned.

‎04-15-2020

I do understand your frustration with cases where users make new connections that the versioning type is set using traditional by default. It is not possible for us to force the geodatabase to only allow branch versioning connections to be established as you can have a mixture of different versioning types in a geodatabase. At some point in the future, it may be possible to request that branch be the default for new connection files. This would be a viable enhancement/idea. If there are specific operations that you don't think should require a branch connection to complete, share these. In the meantime, I suggest that you continue to educate users about the importance of always checking the Geodatabase connection properties for the connection to ensure that branch is set for the versioning type. They can also run the tool to update these. Update Geodatabase Connection Properties To Branch—Data Management toolbox | Documentation

‎01-29-2020

Thank you Rushi for answering - here is the section that will be released in the 2.5 ArcGIS Pro web helps that explains the types of data types that are supported. The key factor here is that geodatabase replication is built on top of traditional versioning. Newer services based datasets created in ArcGIS Pro like the utility network and parcel fabric use branch versioning when implemented in enterprise geodatabases. When the ArcGIS Pro 2.5 documentation goes live early in February, the following page can be referenced: https://pro.arcgis.com/en/pro-app/help/data/geodatabases/overview/introduction-to-distributed-data.htm

‎01-28-2020

I am wondering if your utility network datasets contain data? Currently, the Add Tier process is expected to be completed during the initial configuration stage. This is due to the process adding a not nullable field to certain network datasets. You cannot add a not nullable field to a dataset that contains rows/data. We are tracking an enhancement to make a change in the implementation for a future release. Workflow topic on adding a tier: Define a tier—ArcGIS Pro | ArcGIS Desktop Geoprocessing tool: Add Tier—Utility Network Toolbox | ArcGIS Desktop

‎01-28-2020

It seems like there is something that is causing the connection to portal to timeout before the asset package import is completed successfully. I have seen some cases where the import time is increased due to open maps in your project - have you checked to ensure there are no maps in your project open? Apply Asset Package—Tool Reference | ArcGIS Solutions It is recommended to close all maps in your project before running this tool. @ Electric and Gas‌

Online Status	Offline
Date Last Visited	‎07-06-2026 06:46 AM

My Ideas

Latest Contributions by MelissaJarman

Re: ArcGIS Pro 2.6: Connected tracing ends up with “No valid starting locations found”,

Re: Blog discussion - branch versioning

Re: Blog discussion - branch versioning

Re: Blog discussion - branch versioning

Re: ArcGIS Pro 2.5: The utility network “no junction edge rule” error is popped up,

Re: ArcGIS Pro 2.5: How to display flow arrows and set flow direction in the utility network,

Re: ArcGIS Pro 2.5: The utility network “no junction edge rule” error is popped up,

Re: Why are errors duplicated in Arcgis Pro?

Re: Blog discussion - branch versioning

Re: ArcGIS Pro 2.5: adding subtypes for utility network device feature class ends up with error,

Re: Why utility network layer is not versioned?

Re: Turn on Branch Versioning by default when Staging a Utility Network

Re: Does Utility Network support GDB replication?

Re: ““Add tier” tool to a utility network is not working as expected and ends up with an error”

Re: "Must be connected and signed into the portal" error when using the "Apply Asset Package" Geoprocessing Tool

View properties of database sequences

Re: branch versioning historical moment

UC 2022: Branch Versioning (resources)

Re: REGISTER AS VERSIONED = EDITS TO BASE (GREYED ...

Re: Feature services vs Direct database connection...