Latest Contributions by RobertKrisher

You need to determine which code you deleted from the domain and re-add the original code and description to the domain before you can reassign it.

What type of dataset is this? If its something with a system tier you could create a network diagram using that subnetwork.

@CristinHolmgren2 are you deploying this to a mobile geodatabase? or a file geodatabase? or enterprise geodatabase? Don't use a file geodatabase when working with associations, they are painfully slow for that. If you are using a mobile geodatabase, make sure it is on an SSD that is local to the machine that is running the tool. You could turn on simple build logging to see timestamps of when the various events are running.

What I'm saying is that you didn't need to extend the domain, you should have use the existing domain and values, just update the descriptions to match the customers data. I have already provided a proposal of how you could have mapped their values to the original values. You should be able to incorporate that into your data migration going forward, and if you need to fix it right now you can adjust the data and schema in the asset package to make the correction. You can see the bitsize in the network properties. Because you are using an asset package to build your utility network, refer to their documentation for hot to control the size of an inline attribute: Utility Network Package_Asset Package Reference.pdf

There is no such thing as creating a new association role. The roles are none, container, and structure. If you are setting the association role of an asset type (e.g. handhole) from None to a Container you will be able to do that as long as the topology is disabled. If the Handhole is already set to be a Structure and you want to make it a Container, then you are altering the association role, which is not allowed once you have enabled the network topology. Based on the error you are receiving, it sounds like this is the case. If you want to alter an association role after enabling the network topology you will need to go back to an asset package, remove any containment/attachment rules associated with it, change the role in the asset package, add new rules, then re-deploy your utility network. You can see what the asset type's current association role is by opening the tool or looking at the network properties (choose the show default values option to make it clearer). The association role of the handhole in the utility network foundation is structure.

The domain you have configured to set the bitsize of your phasesenergized domain (Electric_Phase_Attribution_All) only allows for 3 bits (max value = 7) The domains you have assigned to your features appear to have a maximum value of 14, which requires 4 bits. Furthermore, it looks like you just added RYB values onto the end of the domain instead of using the existing coded values and renaming the descriptions. This is important, because the way you have done this does not allow for the bitwise combination of the different phases, which will result in phase propagation not working correctly. It looks like RYB = ABC, and my guess is if you look at the original coded values in your source data you will see that the integer values from your original domain matched (R=4, Y=2, B=1, and RYB=7). After inspecting your data, it appears that you should have just mapped your phasing values to the existing domain values instead of extending the domain.

You should be able to set an association role after you've enabled your network topology. You just can't change or unassign it, and you will need to remove any existing rules before you can change the role. All the restrictions are listed on the Utility network management tasks topic in the online help.

@AllanBenvin_yyc Because SDE doesn't use a static query for accessing the data like a view does. Take a look at how where clauses are applied to the branch version analytic and it will start to make sense. If you have a limited number of access paths you're supporting with dynamic views, you can recreate optimized queries similar to what ArcGIS Pro is doing. But this is an advanced activity that requires a strong understanding of SQL. Also, it's not doubling the storage requirements of the table. You're duplicating the storage of only the active rows in the table, not the active rows + N years of history.

please open a case with support

Can you show a screenshot of all your network attributes? along with the full attributes of one of the features that has this error?

Lines don't need to be split in order to have connectivity in the utility network, and the Water Utility Network Foundation is configured to allow for connectivity at any vertex along the line. Asset types can be configured with an Edge connectivity policy that controls whether connectivity is allowed at any vertex or only at the endpoints, so if you add any new line asset types you need to remember to set an appropriate edge connectivity policy (the default is end vertex only).

When this happens you should look at the locks in the database and see who else has a lock on that version. Read the Manage geodatabase locks topic in the online help to learn more.

The Path trace doesn't use subnetworks. This means that it shouldn't be used when subnetworks, propagation, or directional terminal configuration would affect the outcome of a trace. Its also designed to evaluate multiple paths and choose the most suitable path. If you evaluate each domain using that criteria you'll see that electric distribution networks are not suitable for the Path trace. The Path trace is useful for Telecom or other networks where you have a significant amount of indeterminate flow you need to evaluate (gas, water, electric transmission).

The Migration Wizard creates a brand new database, schema, and loads the data each time it is run. If all you need to do is reload one or two feature classes, or you've made changes to the schema or data, it is best to use the data loading workspace created by the tool to reload just the desired tables. This is discussed in some detail in the Expanding on the Migrate to the utility network tool community article.

@angiexx1 Doing a Path trace is an electric network is not recommended because it will ignore the flow direction of terminals and your sources. Having said that, its probably not finding a path because either your max hops is too low or the features belong to different circuits (i.e. there is no traversable path between the two points).

Online Status	Online
Date Last Visited	an hour ago

My Ideas

Latest Contributions by RobertKrisher

Re: Utility Network – ERROR 004049 Unable to modify domain, one or more asset types have been deleted

Re: Has anyone created a One Line Diagram or has employed a third party?

Re: 14 Million Associations - Best way to load to Utility Network?

Re: ERROR 003856:* The max value of the domain exceeds the bit size of the network attribute while applying asset package

Re: Association Roles/New Rules

Re: ERROR 003856:* The max value of the domain exceeds the bit size of the network attribute while applying asset package

Re: Association Roles/New Rules

Re: Branch Version Sql Views - Utility Network

Re: Validate Network Topology Fails ArcGIS Pro 3.7 for Water UN, Sewer UN

Re: ERROR 003856:* The max value of the domain exceeds the bit size of the network attribute while applying asset package

Re: Water UN Data Cleanup

Re: Edit operation failed. Message: Cannot acquire a lock.

Re: What is the difference between the Stop and the barrier in the tracing? ArcGIS pro v3.7

Re: Is Migration wizard migration one time activity?

Re: What is the difference between the Stop and the barrier in the tracing? ArcGIS pro v3.7

Re: How to determine Version Name from OnPost WebH...

Re: Combine Utility Network and File GDB into one

Re: 14 Million Associations - Best way to load to ...

Re: Association Roles/New Rules

Re: ERROR 003856:* The max value of the domain exc...

European Utility Network Community (UNC)

APAC Utilities Community of Practice