CSM workspace tabs and filters
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-04-2025 05:04 AM
I am in the process of building a new page variant in the CSM workspace which contains tabs. I have some single score data visualisations on each tab. The tabs all have their own filters. However, if I have a filter set in one tab, all my single scores on the other tabs are filtered too.
I can see that the follow filters option in "Data update" has the option to bind the data, but ive not yet worked out how I can do this. Can anyone provide any guidance on this?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-05-2025 03:31 AM
Hi @M_A,
you mentioned CSM Workspace and also sing score, so it is related to report/dashboard, could you please provide more details, screenshot or anything else to understand it better?
/* If my response wasn’t a total disaster ↙️ ⭐ drop a Kudos or Accept as Solution ✅ ↘️ Cheers! */
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-05-2025 07:37 AM
hi @M_A ,\
By default, when you place multiple data visualizations (like Single Score or List components) on tabs within the same page, they often share the same parent data resource (e.g., the same Aggregate or Data Table resource).
So when you filter in one tab, it updates the parent data resource — which naturally updates all other widgets bound to the same resource, even those hidden under other tabs.
✅ How to fix this
To stop filters from “leaking” across tabs, you need to decouple the data sources:
Create separate data resources
Instead of using the same Aggregate/condition for all Single Score visualizations, create one data resource per tab.
This way, filters on Tab A update only Data Resource A, and so on.
Bind filters locally
In UI Builder, select your Single Score or List.
Use the Follow filters → Data update option carefully:
Choose to bind the filter only to the specific data resource for that tab.
Avoid binding it to a shared context-level filter that affects the whole page.
Scoped filters
If you have a Filter component per tab, make sure each filter’s output is bound only to that tab’s data resource.