Dashboard Using a 'filtered' view to filter a 2nd 'filtered' view in a Dashboard

[Harriswe]

Is it possible to use a filtered view in a dashboard to filter a 2nd filtered view, akin to showing details.

I have a dashboard with the following:

1. List of Regulations filtered by jurisdiction (country)
2. The details shown for a selected regulation
3. The articles shown for a specific regulation (only this 2nd filtered view does not change when I select the Regulation.
4. To change the Article view I have to use a drop-down list in a form. (Not as user friendly)
5. Once the correct articles are displayed, clicking one shows the Article details
6. Article detail view shows the details for the article selected.
7. Is it possible to use the filtered view of Regulations to filter the list of articles?
8. Tried using an action to update the Regulation in the form. Didn’t work
9. Tried using a trigger action on the filtered list of Regulations, to update the form. Didn’t work

See image below.

)

Q: Would like to know if what I am attempting in possible in a Dashboard?

[Suvrutt_Gurjar]

Could you please update if the table that has list of articles refers the regulations table, meaning is the list of articles table the child table of the regulations table?

I believe , if so and also if the dashboard has interactive mode enabled, then tapping on one of the regulations in the list of regulations will display the corresponding list of articles in the articles table

[Harriswe · Accepted solution]

Hi @Suvrutt_Gurjar,

In answer to your question:

• A Regulation can have many Articles
• An Article can have only one Regulation

So there is foreign key on the Article table pointing to the Regulation.

So in theory: clicking on a the list of filtered regulations, should be able to filter the list of Articles. That was the premise I started off with.

I think I know what the problem is. In the Articles table the Regulation was of type enum. Changing this to be of type Ref sorted out the issue.

See screenshot.

So it now works as described. Thank you @Suvrutt_Gurjar for helping me trace back my steps and to think about how the relationships were defined.

A good point of learning for future Dashboards.

[Suvrutt_Gurjar]

Thank you for the update. Nice to know you got the solution.