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; } } }

Apply Asset Package with configuration table

PierreloupDucroix

Hi,

I try to apply an asset package using the d_configuration table to remove tiers, subtypes ad everything that depends on it.

I started with an existing asset package, then created the d_configuration table with a new configuration field.

With older version, I think I could choose between True or False to include / not include a specific item. (see https://www.powereng.com/library/extending-the-utility-networks-base-configurations-2-of-2)

Now with ArcGIS Pro 2.9 and untools 2.9.1 I have three values

- not evaluated

- Evaluated

- Exclusive

Whatever value I choose for a group of subtypes I want to (not)include, everything is applied when I run Apply Asset Package.

Can anyone explain how to use it properly ?

@PaulLeBlanc1 @MikeMillerGIS ?

タグ付けされた投稿をもっと見る

Accepted answers

MikeMillerGIS

When you applied the asset package, did you uncheck the configuration?

Here a a definition of the values

Not evaluated = This was false before, the row is not evaluated as part of the configuration

Evaluated = This was true before, If set, the this entry will be removed if this category is not applied only if true/evaluated if not set in any other category that is applied

Exclusive is new. If set, the this entry will be removed if this category is not applied only regardless of any other settings in other applied categories.

All comments

GISP00

Thank you for trying to locate the Power Eng articles. I reached out to the author. He replied that he will assist with my request when it is convenient for him to chat further.

In the meantime, thank you for suggesting the use of the Analyze Network Data GP Tool. The Esri team keeps publishing new tools faster than I can keep up with improving my methods to migrate to a UN.

I will incorporate that GP Tool into my workflow, possibly replacing the Summarize Errors step that Robert Krisher suggested in his Load Data tutorial.

For others that might find this thread while looking for D_Configuration table information, below is a blog I found this morning. The second link is a tutorial for the GP Tool that Mike suggested.

Using the D_Configuration Tables Tutorial by John Alsup and Robert Krisher

Using the Analyze Network Data GP Tool by Robert Krisher

MikeMillerGIS

I cant find the Power Engineer articles, I think they are forever gone.

Here is the link to the most current help on the d_configuration table - https://doc.arcgis.com/en/arcgis-solutions/latest/tool-reference/utility-network-package/pdf/Utility%20Network%20Package_Asset%20Package%20Reference.pdf

Yes - you can definitely use the d_config table at this point, but first, before exporting back to Asset Package, try the Analyze Network Data GP(part of pro). It has a complimentary tool to resolve errors.

For fields, you can also just delete them, unless they are set as a Network Attribute.

GISP00

@MikeMillerGIS thank you for providing the links to more information on the D_Config table. However, 4 years after this thread was created the links provided above redirect to other pages and not the articles intended. For example https://solutions.arcgis.com/utilities/help/utility-network-automation/ redirects to https://www.esri.com/en-us/arcgis/products/arcgis-solutions/overview

And after Power Engineers was acquired by WSP, the Power Eng articles 1 & 2 are not found. Can you provide new documentation on the D Tables or point to a blog that shows how to use D_Config tables in different scenarios?

I am trying to understand when and how to use the D Tables and its configurations so that I can iterate a UN migration several times before final production migration.

Process seems to be:

Simple Data Mapping -> Data Reference workbooks -> load data -> Sync C Tables -> Asset Package to Geodatabase (file geodatabase) -> Enable Network (errors only) -> Summarize Errors -> review and understand UN using Pro. Then I make a few rules or modify existing Domains in the file GDB.

After quickly getting to a UN in a file geodatabase, now I want to perform a production migration to an Enterprise GDB. Do I create a new Asset Package from the modified UN from the last iteration above, then modify the D_Confg tables (configure to remove fields or Asset Groups/Types), and the run Asset Package to Geodatabase?

I am trying to avoid going all the way back to the Simple Data Mapping workbook and starting over. I think the D_Config table seems to be a intermediary to remove fields or asset group/types we don't want in final production.

VanessaSimps

I would love a little more information about all of this in the documentation! The information on this page isn't overly helpful for newbies! And I haven't found much else out there to help explain how to use the d_configuration tables.

MikeMillerGIS

The help is located at the below link, but does not have the information I posted above. I will work with the doc team to get it added.

https://solutions.arcgis.com/utilities/help/utility-network-automation/

I know it is a little hard to grasp at first, but are some reasons we had to implement it this way. I am glad it is working for you now!

PierreloupDucroix

Hi Mike,

Thank you for the clarification.

So if I want to exclude some tiers/subtypes, I need to set everything to 0 (Not Evaluated) except the specific items I want to exclude, which I set to 1 (Evaluated) OR 2 (Exclusive) if I have several configurations and want it to be excluded anyway.

Then the weird part is I need NOT TO check the configuration when applying the asset package... It is a bit counter-intuitive, but it worked !

I couldn't find any documentation about this behavior, will there be an official doc ?

Thank you again

Regards

MikeMillerGIS

When you applied the asset package, did you uncheck the configuration?

Here a a definition of the values

Not evaluated = This was false before, the row is not evaluated as part of the configuration

Evaluated = This was true before, If set, the this entry will be removed if this category is not applied only if true/evaluated if not set in any other category that is applied

Exclusive is new. If set, the this entry will be removed if this category is not applied only regardless of any other settings in other applied categories.

会話に参加する

サインインしたメンバーは投稿、更新のフォローなどができます。初めてですか？無料アカウントを登録してください。

クイックリンク

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