Import associations in Utility Network

311
4
Jump to solution
10-03-2023 02:41 PM
DeepikaJain01
New Contributor III

Dear Team

I am new in building the Utility Network. I have applied Asset Package and have built the UN from the foundation solution. The issue is it has not imported the associations, the "Association Status" field is null for all my Feature classes. Can you please help me as to how can I update the associations for all the Communication and Structure Feature classes.

Thank You

0 Kudos
1 Solution

Accepted Solutions
RobertKrisher
Esri Regular Contributor

@DeepikaJain01 oh, that's your problem. You need to create all the objects in the asset package and populate the C_Assocations table with the foreign keys and other information in order to relate the objects. Setting the association status of a feature to be a container isn't sufficient, as it doesn't tell the system which features should be used as its content.

The bug that Pierreloup described means that after you apply your asset package (with all your associations) that the associationstatus field will be out of sync.

View solution in original post

0 Kudos
4 Replies
RobertKrisher
Esri Regular Contributor

The association status field is a system- maintained field that will be populated automatically based on the types of associations present for a feature.

When you say that there weren't any associations imported, were there any errors during the apply asset package process? Did you populate the C_Associations table in the asset package ahead of time? Are there any errors associated with your associations?

0 Kudos
DeepikaJain01
New Contributor III

Hi @RobertKrisher 

There were no errors when I applied the asset package, I am not sure what has caused the issue. Let me reapply the asset package and see if associations get imported. Also, I didnot populate C_Associations table in Asset package. I thought defining the Association status in asset package in the feature classes is sufficient.

0 Kudos
RobertKrisher
Esri Regular Contributor

@DeepikaJain01 oh, that's your problem. You need to create all the objects in the asset package and populate the C_Assocations table with the foreign keys and other information in order to relate the objects. Setting the association status of a feature to be a container isn't sufficient, as it doesn't tell the system which features should be used as its content.

The bug that Pierreloup described means that after you apply your asset package (with all your associations) that the associationstatus field will be out of sync.

0 Kudos
PierreloupDucroix
Occasional Contributor II

Hi,

there is a bug where you need to import associations after enabling the topology, because the Association status is not calculated if you import before anebling topo.

Maybe you can check that first.

0 Kudos