Latest Contributions by MelissaJarman

The Dirty Areas are symbolized using the status field -  The Status attribute field uses bitwise encoding to represent the operation that created the dirty area. For example, a deleted feature is represented by bit 1 and is displayed with a status of 2 (2^1 = 2). These values are summated if multiple operations led to the creation of the dirty area. A Status Description field is displayed in the pop-up expression to provide additional information about the operation that created the dirty area. You can review the following pages to see if they provide you with help on how to use Errors.  Errors  Error management ... View more

There should not be issues with creating multiple UNs in the same geodatabase. The non-spatial object tables will be created with _1 appended to the end of them. MelissaJarman_0-1610554880539.png   The UN system tables, domains, etc all use the OBJECTID from the GDB_ITEMS table for the utility network they pertain to as part of the naming convention. It might be a good idea to do the same for any user-defined domains that are created in the geodatabase to keep up the organization. Here are a few domains with the naming convention mentioned: MelissaJarman_1-1610554949038.png   ... View more

Sarah - Thanks for bringing this up. This is a result of the Modify Associations pane being reworked to support nonspatial objects for the utility network. We will work on getting this learn lesson updated for the updated UI of the Modify Associations pane.  You simply need to use the Add Features or Load Selected buttons in the pane to set the active item. ... View more

Lindsey -  It sounds like from your workflow that you are experiencing expected behavior for updating subnetworks in a named version. In a named version only those rows (network features) that are edited will be updated by default. Since the subnetwork features were not edited when you disabled/reenabled the device feature as a subnetwork controller, they are not being updated with the subnetwork name during update subnetwork. This is one of those gotchas that definitely tripped me up too. You will need to reconcile/post with default and update subnetworks in default. I would recommend performing these operations in default and then reconciling your named versions. If there is an absolute need for this to work in a named version, you could change the Edit Mode for Default Version to With eventing (new at 2.6/10.8.1).   See the following topic for more information: Update subnetworks    Let me know if you can try the following: 1. Make a small edit to one of the subnetwork features in the named version and verify that update subnetworks does update the subnetwork name attribute for this feature due to the edit. 2. Reconcile/post with default, run update subnetwork in default, and then reconcile again in the named version. ... View more