nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Import associations in Utility Network

DeepikaJain01

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

Encuentra más publicaciones etiquetadas con

Accepted answers

rkrisher

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

All comments

jhd011

I confirmed the same issue on my end. What were your findings and/or resolution from the support case?

rkrisher

@NSimmons44 I recommend you log a support case on this. They will be able to help you with identifying any known issues and workarounds.

NSimmons44

I was not able to find this bug logged anywhere, but wondering is there another resolution or way around this issue? Loading all of the data into the asset package is not an option for us at this point. We are applying asset package, then loading all data. We have tried importing associations both before and after enabling topology, but haven't gotten the association status field to update correct for all features. However, even though the association status doesn't always update, the associations still exist, as shown in the image below.

The status seems to only sometimes get updated for structural attachments, but containment seems to be correctly updating for all relevant features.

@RobertKrisher do you have any other ideas or workarounds for this issue?

rkrisher

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.

DeepikaJain01

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.

PierreloupDucroix

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.

rkrisher

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?

Únete a la Conversación

Los miembros registrados pueden publicar, seguir actualizaciones y más. ¿Nuevo aquí? Regístrate gratis.

Enlaces Rápidos

Community Help
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.