Dynamic filter with different filters in single Dashboard

Atik
Tera Contributor

3 weeks ago

 

Hello Everyone,

 

I am currently working on a dashboard where we are implementing a dynamic content block. In this block, we have created a dropdown to pass year values, for example:

 

2020
2021
2022
2023
2024
2025

 

The dashboard contains multiple reports across three different tabs. These reports are based on different tables such as kb_knowledge, task, and cmdb_ci.


Most of the reports use filters based on sys_created_on (between), while some reports use sys_updated_on, and a few have other date-related filters.

 

Initially, I was planning to group the reports tab-wise and apply separate filters for each tab accordingly. However, based on the client’s dashboard design and layout, the reports are mixed across different tabs with varying tables and filter conditions.

 

I would appreciate your guidance on whether there is any recommended or possible approach to handle such a scenario effectively and achieve the desired filtering behavior.

 

Thank you in advance for your support and suggestions.

 

Thanks,
Atik




0 Helpfuls
  • 596 Views
1 REPLY 1

Matthew_13
Mega Sage

3 weeks ago

Hi my Friend!

 This is a pretty common situation, and you’re not doing anything wrong. The main issue is that one dropdown can’t cleanly control multiple reports that all use different date fields. Tabs don’t really help either they are just visual groupings, not separate filter scopes.

The approach that usually works best is this:

  • Keep one Year dropdown on the dashboard so the user experience stays simple.

  • Don’t try to use a single dashboard level filter.

  • Instead let each report handle the year filter on its own using the date field that makes sense for that report:

    • Some reports filter on sys_created_on

    • Others on sys_updated_on

    • Others on their own date field

All the reports read the same selected year I found but each one applies it to the correct field.

It does mean a bit more setup per report but:

  • You avoid fragile tab-based logic

  • You dont have to duplicate dashboards

  • The behavior stays predictable and supportable

If possible, it also helps to document which date field each report uses so future updates don’t accidentally change the meaning of the data.

In short: there isn’t a single “magic” filter for mixed tables and mixed date fields. A shared Year selector with report-level date logic is the cleanest and most reliable solution.

 

@Atik - Please mark as Accepted Solution and Thumbs Up if you found Helpful!!

0 Helpfuls