Utility Network Trace Results – Table Selection Does Not Trigger Related Table Actions

[RG2]

Utility Network Trace widget in ArcGIS Experience Builder (Enterprise 11.5)

After running a trace:

• The Table widget correctly displays and highlights the traced records.

• However, the configured action (for example, selecting related records in another table) does not trigger.

• If a record is manually clicked in the table, the action fires immediately and the related table updates as expected.

Seems that the selection created by the Trace widget is visible but does not behave like a real selection event within Experience Builder.

Am I missing something in the configuration, or is this a current limitation of the Trace widget?

@AlixVezina @RobertKrisher @MikeMillerGIS 

[AlixVezina]

Hi @RG2 ,

Have you configured a Message action between the Utility Network Trace widget and related layer data source, to select the related records when a trace is returned? Message actions only go one level deep, so you'll need to configure the action between the Utility Network Trace widget and the related layer itself, rather than between the Table widget and the related layer.

Message action example below (this is not utility network data):

Steps:

1. Go to the Action panel in the Utility Network Trace widget settings
2. Under Message action, click Add a trigger
3. Select a target: Record selection changes
4. Select a target: Framework / Data
5. Select an action: Select data records
6. Trigger data: the layer being selected by the Utility Network Trace widget when trace results are returned
7. Action data: the related layer, related to the trigger data layer above
8. Conditions: Use layer's relationship (note: you can also mimic relationships based on common field values)

[RG2]

Hi Alix,

Just to summarize what I’m seeing from additional tests on my side:

1. When using subtype group layers (as typically done for Utility Network in web maps), the option to select related records is not available in the Trace widget. Even when trying to mimic the relationship using a common field between the subtype layer and the related table, the trace results do not trigger any selection in the related table.

2. When switching to a flat feature class (no subtype group layers), the option to select related records does appear in the Trace widget. However, running the trace still does not trigger selection in the related client table. A manual click on the same feature in the map, using a map-based trigger, selects the related records immediately.

3. This makes me wonder how selection works internally in the Trace widget. Is the “selection” created by the Trace widget considered a real selection event in Experience Builder (i.e., one that fires a Record selection changed message), or is it a visual/result highlight that does not propagate as a standard selection?

4. Have you been able to make this work in Utility Network datasets, where a trace in Experience Builder successfully triggers selection of related records in another table? If so, it would be very helpful to understand the exact setup.

Thanks for you support!