Hello Dan,
Thank you for your response.
Following is a description of part of my system:
- I have a table with about 10000 records (fossil specimens - the specimens table)
- The table is related to a FC with about 350 points (localities where the fossils were found - the localities FC) in a many-to-one relationship
- The specimen table has a field that contains the genus of the specimen. The genus is not an unique field and there’re about 130 values
- There is a table that contains the ~130 genus values - the genus table
What the user of the app wants to achieve is:
- Select a genus value from the unique list. Let say genus==X
- Filter the specimens by the selected genus and get only the specimens with genus X
- Filter the localities list and the localities map accordingly, so they display only the localities where specimens with genus X were found
Following are the widgets of the page:
- A filter widget based on the genus table - W1
- A list widget based on the genus table - W2
- A list widget based on the specimen table - W3
- A list widget based on the locality FC - W4
- A map widget based on the locality FC - W5
This is how it is implemented today:
- The user selects one genus value in W1
- The filter widget does not have a trigger so it filters W2 but it doesn’t select anything
- The widget W2 shows the genus selected in W1
- The user selects manually the one genus in W2
- This step could be done automatically if the widget filter could trigger some selection action on a list
- If there’s something selected from a previous run, the results are strange what may be quite confusing to the user.
- The selection action on W2 triggers a filter on the specimen table (framework) and a selection on the same specimen table. As a result, W3 is filtered and its records are selected
- If I apply a counter on the amount of records, for an expected large result, the result is either 1980 or 99 but not the real amount. It looks like there is a limit on the amount of records selected
- The user must manually unselect one record in W3 and select it again
- This is because W3 should trigger a filter on the localities table (framework) and on the localities map but this trigger doesn’t work unless the user does some manual selection
- W4 and W5 display the localities required, the ones related to specimens with the selected genus
- The localities displayed are less than the expected because of the limitation on the amount of specimen records selected
I hope my explanation is clear because due to a problem in my enterprise portal I cannot prepare screenshots to show the widgets and the data behind them.
Thank you in advance,
Marcelo