How-To - Conduit Manager - Set Default Values for Duct Features

Version 5

    Solution

     

    A known bug, MM55233, causes UFM to use information for the default value of new ducts created by UFM instead of using the Default Value of the field. This only affects Ducts created prior to their Duct Bank's association to a conduit. If the usual workflow for your users is to:

    1. Create the conduit
    2. Configure the ducts within the conduit
    3. Place the duct bank from the conduit configuration

    ...then these steps do not apply to your workflow. Follow the directions below to configure the default value for your duct fields.

     

    1) In the geodatabase's domain list, create the following domains if they don't already exist:

     

    Default No Indicator

    Field type: Long integer

    Domain type: Coded Values

    Code

    Description

    0

    No

    1

    Yes

     

    Default Yes Indicator

    Field type: Long integer

    Domain type: Coded Values

    Code

    Description

    1

    Yes

    0

    No

     

    Default No Indicator

    Field type: Text

    Domain type: Coded Values

    Code

    Description

    N

    No

    Y

    Yes

     

    Default Yes Indicator

    Field type: Text

    Domain type: Coded Values

    Code

    Description

    Y

    Yes

    N

    No

     

    The order of these values matters! Ensure both the coded values and the order of the value-description pairs match the above.

     

    2) For each field on the Duct feature class with an indicator field (e.g., Available), use the indicator domain for that field's data type with the preferred default value as the first item in the domain.

     

    For example, ducts are typically first created with Available - Yes, Occupied - No, HasSubducts - No. These values then get changed later as the ducts have conductors and cables assigned. Thus, the field Available would have "Default Yes Indicator" assigned, Occupied would have "Default No Indicator," and HasSubducts would have "Default No Indicator." To be consistent, ensure that the default value set for the Available field on the DuctDefinition table in ArcCatalog (i.e., a default defined through the usual methods) matches the default chosen for the Duct feature class.

     

    This article will be updated with a product resolution for the bug, if one becomes available.