Hello,
I wanted to know if there was a way, by editing the code I imagine, to change the way the data actions work.
I'm currently using the Filter widgets to modify my building Feature Layer on the Map widget.
I have tables with offers and transactions and with a selection action set on the structure, I can use a common ID to filter or select my offers and transactions in my Table widget.
I know that the ‘Group Filter’ allows me to filter my table at the same time, but this IMPOSES having the columns from my Feature Layer building in my offer and transaction tables.
Except that I now have two problems:
1) My users prefer to filter on offers and/or transactions first and then filter on buildings.
=> The problem is that I can't sort the columns that I'll use in the Filter widget to filter my offers and transactions because several transactions can relate to ONE building, which forces me to duplicate my building, which is rather annoying, especially on the map (overlay of points).
2) I could filter my offers and transactions and then SELECT them so that it filters the buildings using the select action, but the problem with that is that it's really not efficient or intuitive to ask a user to SELECT on a map the elements that they want to see updated in another widget.
The most logical, quickest, most effective and most ergonomic way would be for the user, when filtering the building data, to simply have the system interpret this in the same way as when selecting on the map and filtering ALSO on the Table widgets.
Except that this functionality doesn't seem to be in ESRI's plans at all, so I'm turning to you to see if anyone has already manipulated a bit of the Experience Builder code to succeed in implementing this principle?
Have a nice day,
