Release notes for 2.6

The release notes for the Utility Network Package Tools toolbox are described below.

untools version 2.6.2

The November 2020 release of the Utility Network Package Tools toolbox includes the following updates:

  • Updated the Apply Asset Package tool:
    • Resolves an issue with subset of domain networks.
    • Relaxes validation for Subnetwork Configuration
    • Improves validation for propagation

untools version 2.6.1

The September 2020 release of the Utility Network Package Tools toolbox includes the following updates:

  • Updated the Apply Asset Package tool:
    • Converts GUID fields that start with GlobalID_ to GlobalID type in the target geodatabase.
    • Ignores any non utility network controller dataset.
    • Supports asset packages with only structure networks.
    • Preserves GlobalID values when the asset package has a GlobalID field type and the target is a file geodatabase.
    • No longer does any post-processing when there are 0 utility network rules.
    • Validates database sequence names for validity and length.
    • Provides a warning when / is present in asset group or asset type names.
    • Blocks :: in subnetwork and subnetwork controller names.
  • Export Asset Package ignores any non utility network controller dataset.

untools version 2.6.0

The July 2020 release of the Utility Network Package Tools toolbox includes the following updates:

  • Updated the Apply Asset Package tool:
    • Validates that codes and descriptions in workspace domains match.
    • Upgrades the asset package version to 2.6 to support new properties in the utility network.
    • Supports default subtypes values set by the Set Default Subtype tool.
  • Blocked the Apply Asset Package and Stage Utility Network tools when the default version is protected.
  • Added support for renaming terminal configuration paths.
  • The D_Configurations table now removes subnetwork summaries if subnetline fields are removed.
  • Added validation to the D_Configurations and D_Rename tables to ensure values are valid.
  • Only add attribute rules that use calculation/validation required only when the workspace is an enterprise geodatabase.
Top