Experience Builder: Need solution for property-based data display - issues with both Selection and Filter approaches

[ola]

I'm developing a property information web application in the hosted version of Experience Builder (ArcGIS Online) and encountering challenges with both selection and filtering approaches when trying to implement a specific property information workflow.

Current setup: My application works with two related datasets:

• A polygon layer representing property boundaries
• A point layer containing various property-related data points (such as ownership information) These layers are related through a common identifier field (let's call it 'propertyID')

Current attempts and issues: I've tried two approaches, each with its own problems:

Approach 1 - Using 'Selected Features': When configuring the list widget to display 'Selected Features', I've encountered this behavior:

• Users select a property polygon using the Select widget
• When users click on a property data point in the list, it unexpectedly unselects that item
• This unselection prevents the Feature Info widget from displaying properly
• The behavior disrupts the natural flow of exploring property information

Approach 2 - Using 'Filter': When switching to using filter instead of selected features:

• The list widget displays ALL points in the entire dataset when no property polygon is selected
• This creates a confusing user experience where users see all possible data points before making a property selection
• The interface becomes cluttered and less intuitive for users trying to find specific property information

Desired functionality: The application should work as follows:

1. Initially, the list should be empty until a user selects a property polygon
2. When a user selects a property polygon on the map using the Select widget, the application should display only the data points associated with that property
3. The list should be filtered to show only relevant property information, but the points should not be in a selected state
4. Users should be able to click any item in the list to view detailed information in a Feature Info window without triggering selection conflicts

Technical questions:

1. Is there a way to achieve this workflow that avoids both the selection conflicts and the initial display of all points?
2. Are there specific widget settings or combinations that would allow for:
   • An empty initial state
   • Property-based filtering when a polygon is selected
   • Proper pop-up functionality for listed items
3. Could this be achieved through a combination of filters and expressions, or is there another approach entirely?

Current setup:

[JasonBOCQUET]

Hi @ola i have a similare problem with owners of a building. I have one layer with my buildings, and another layer with the owners of each buildings. 

I"ve try in a first way the selection, but it was not very practical for my users to made a selection of what they want to see. 

So i've created a Relationship class between my 2 data, by using a similar id to make a link between the two data sources. With a little bit of arcade i've created on map viewer a popup so when my user click on a building, they can see which owners are on the building.

I wish i can give you a new way to explore to manage your data. 

Another way to filter your second data source depending of the first is to have a common ID between the sources, copy the fields that you used to filter the first data source on the second data sources table and set the filter to filter the second data sources by these new field. With that, you can simulate a dynamical approach.