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:
- Initially, the list should be empty until a user selects a property polygon
- 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
- The list should be filtered to show only relevant property information, but the points should not be in a selected state
- 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:
- Is there a way to achieve this workflow that avoids both the selection conflicts and the initial display of all points?
- 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
- Could this be achieved through a combination of filters and expressions, or is there another approach entirely?
Current setup:
