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

Utility Network Package toolbox 3.3 release notes

PaulLeBlanc1

The 3.3 release of untools contains the fixes from untools 3.2.0. For more information, see the 3.2 release notes.

untools 3.3.4 - June 2025

Export Asset Package
- Resolve BUG-000174483
Assign Terminal Connections
- Flip logic when assigning terminals in sink based networks (see this post)
Apply Asset Package
- Sync delimiters between CSV files and schema.ini

untools 3.3.3.1 - December 2024

Create Utility Network Associations
- Restores behavior of GP tool broken with untools 3.3.3 (see this post)

untools 3.3.3 - November 2024

Assign Terminal Connections
- Resolve issue with the "Honor Digitized Direction" using the incorrect upstream and downstream terminal
- Optimize and refactor code to scale on larger datasets
Apply Asset Package
- Resolve issue when using a D_Configuration table and applying a subset of domain networks

untools 3.3.2 - August 2024

Apply Asset Package
- Expose option (untools.common.settings) to run Compact. Previously this was always True, but now defaults to False.
- Improve Rename table validation
  - Every row and column is now checked regardless if it is used.
  - Duplicates and length restrictions are now more consistently validated.
Miscellaneous
- Resolve issues with various geoprocessings and input/output parameters from python.

untools 3.3.1 - July 2024

Apply Asset Package
- Support for Utility Network 6 & 7
- Expose options (untools.common.settings) for custom precision/scale on single/double fields
- Resolved issue where standalone tables would not be created in the target workspace
Stage Utility Network & Asset Package to Geodatabase
- Add new parameter to choose the Utility Network version to create (6 or 7)

untools 3.3.0 - May 2024

Add support for Utility Network version 7
- Big Integer network attributes
- Flow Direction network attribute

Apply Asset Package
- Expose extent environment variable (in Asset Package to Geodatabase)
- Skip tiers whose valid controllers are completely removed by D_Configurations table
- Add support for terminal paths when there are 5 or more terminals
- Skip feature classes removed by D_Configurations table
- Support Data Reviewer attribute rules across tables
- Improve support for Date network attributes
- Validate contingent values on tables without subtypes

Upgrade Asset Package
- Assign missing asset package domains to existing fields

Miscellaneous
- Cleanup locks from arcpy cursors
- Remove extraneous console logger

Finde mehr Beiträge mit dem Tag

Kommentare

PaulLeBlanc1

@gpgisandsky I've not been able to reproduce that behavior, but I believe it should be resolved with 3.3.4

gpgisandsky

hi,

im on pro 3.3.5 + un tools 3.3.3.1. When I try to apply assetpackage to file geodb (empty un v7) the following error appears:

The issue is related to how the CSV was generated by the tool during execution (AP_Workspace0\csv\association001.csv). The tool creates a CSV file using a comma as the separator instead of a semicolon, which is what the import tool expects. Is there a parameter in PRO "or elsewhere that can be changed?

PaulLeBlanc1

@TomEriksencan you try from an non-elevated python command prompt? Internally, the tool is writing to the registry so that might explain it.

I am not sure what else could be the difference from in-app vs standalone python.

TomEriksen

Hi @PaulLeBlanc1 . I'm having issues using untools 3.3.3.1 to stage a utility network with the correct UN version. I'm trying to create a UNv6. Works fine when running inside of ArcGIS Pro, but when running as a standalone python script it creats a UNv7 even though the logging seems to be correct.

I have tested running StageUtilityNetwork as a GPtool, as a notebook and in the python window in ArcGIS Pro 3.3.5 wich results in the correct UN version. But as a standalone it always creates an UNv7.

rlyding

@PaulLeBlanc1 I was hoping you could maybe answer a question on had on the Upgrade Asset Package Tool. I have a post in UN section I linked below. Trying to figure out when the upgrade tool would need to be run and what impact it has on the asset pack.

https://community.esri.com/t5/arcgis-utility-network-questions/question-on-upgrade-asset-package-tool-utility/m-p/1495091

Thanks!

IvanDImitrov

@PaulLeBlanc1 Exactly!
The table is there - it is present and the name is correct (in the Asset Package).
Even this, the tool crashed

PaulLeBlanc1

@IvanDImitrovI am not aware of any issues in this area. This is valid arcade.

FeatureSetByName($datastore, 'LineTypeLib', ['*'], false)

If there isn't a table called LineTypeLib then the runtime error is expected.

IvanDImitrov

Hi, Paul!
Thanks for the good news!
Did the team updated the annoying error, that 3.2.- give:

ArcGIS Pro 3.2.2.49743
untools 3.2.0
Executing from ArcGIS Pro, 0 map(s), activeMap = False
Parallel processing enabled: 6

C:\UN_V2_2\ZERO\AP_Workspace0\xml\ElectricLine_2_EditorTracking-AttributeRules.xml:255
ERROR 002717: Invalid Arcade expression, Arcade error: Table not found LineTypeLib, Script line: 1 [LineTypeLib]
WARNING 000952: Failed to execute (AddAttributeRule).
C:\UN_V2_2\ZERO\AP_Workspace0\xml\ElectricLine_2_EditorTracking-AttributeRules.xml:288
ERROR 002717: Invalid Arcade expression, Arcade error: Table not found LineTypeLib, Script line: 1 [LineTypeLib]
WARNING 000952: Failed to execute (AddAttributeRule).
C:\UN_V2_2\ZERO\AP_Workspace0\xml\ElectricLine_2_EditorTracking-AttributeRules.xml:321
ERROR 002717: Invalid Arcade expression, Arcade error: Table not found LineTypeLib, Script line: 2 [LineTypeLib]
WARNING 000952: Failed to execute (AddAttributeRule).
C:\UN_V2_2\ZERO\AP_Workspace0\xml\ElectricLine_2_EditorTracking-AttributeRules.xml:364
ERROR 002717: Invalid Arcade expression, Arcade error: Table not found LineTypeLib, Script line: 2 [LineTypeLib]
WARNING 000952: Failed to execute (AddAttributeRule).
Failed script Apply Asset Package...
Failed to execute (AssetPackageToUtilityNetwork).

I think the XML is not correctly build here:

return new_id</expression>

<triggering_events_insert>True</triggering_events_insert>

<triggering_events_delete>False</triggering_events_delete>

<triggering_events_update>True</triggering_events_update>

<exclude_from_client_eval>True</exclude_from_client_eval>

<is_editable>True</is_editable>

<batch>False</batch>

</AddAttributeRule>

</workflow>

<rule_name>OperatingVoltage</rule_name>

<rule_type>CALCULATION</rule_type>

<rule_description>Fetch operating voltage</rule_description>

<field_name>maxvoltage</field_name>

<expression>var lookups = FeatureSetByName($datastore, 'LineTypeLib', ['*'], false);

No way the tool to recognise $datastore for a .gdb variant of the tool execution....

Nehmen Sie an der Diskussion teil

Angemeldete Mitglieder können Beiträge verfassen, Updates folgen und mehr. Neu hier? Registrieren Sie ein kostenloses Konto.

Schnellzugriffe

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