Can data actions or filters support multi-step relationships across layers?

BrandonGuo

I have a question related to ArcGIS Experience Builder setup.

I currently have:

• A feature service called "Park"

• Another feature service containing:

  • an Assets layer

  • a Jobs layer

There is a one-to-many relationship between the Assets layer and the Jobs table/layer.

My goal is:

1. User selects a park

2. Automatically filter all assets within that park

3. Automatically filter all jobs related to those filtered assets

The Assets layer contains Park Name/GUID fields, so I can use that for data actions or triggers. However, while the park selection correctly filters the Assets layer, the related Jobs layer does not automatically filter to only jobs associated with those assets.

There is currently no direct relationship between the Park layer and the Jobs layer.

My questions are:

• Does Experience Builder support multi-step filtering/data actions across tables like this?

• Or would it be better practice to move the Park layer into the same feature service and create formal relationship classes between Park and assets. Will Experience Builder honour chained relationships (Park → Assets → Jobs)?

Just trying to understand the best architecture for this workflow before restructuring the data model.

ZachBodenner

Without testing, I recall having trouble daisy-chaining filters that way. However, have you tried both filtering AND selecting the Assets when a park is selected? You might be able to set up a when-selected action when Assets are selected to filter the Jobs. It also kind of depends on the widgets you're using (Table, I'm assuming here?).

Another option would depend on your ability to manipulate the schemas of the data. What is the underlying data setup here? Referenced feature classes from an Enterprise GDB? Hosted Layers? Something else? You mentioned the Assets have the Park Name in them. If you're using referenced geodatabase features, you could write an attribute rule that populates the Park Name (or GUID for that matter) from the Asset into the Job when an instance is added to that relationship. If that's an option for you I could give you examples of that code.