Issue in Platform Analytics Personalize list
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 hours ago
I am facing an issue in Platform Analytics with List Visualizations.
I have two different dashboard tabs that use the same underlying data source, but each tab requires a different set of columns because they serve different use cases.
When I modify the columns in one tab, the same column changes are reflected in the other tab as well. In some cases, the changes also seem to appear in other places where the same data is displayed.
My requirement is to have a fixed set of columns for each tab independently, without changes in one tab affecting the other.
Is there a way to:
- Keep different column layouts for different tabs?
- Prevent column personalization from being shared across tabs or other views?
- Freeze or persist a specific column configuration at the tab/visualization level?
Has anyone faced a similar issue, and what would be the recommended approach?
Thanks in advance.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 hours ago
Hi @KokilaK
I have also observed this type of behavior in Platform Analytics. To address the issue, I recommend creating the required number of List View widgets independently rather than duplicating existing widgets.
Each List View widget should be configured according to its specific reporting requirement and given a clear, consistent, and meaningful name. Avoid creating unnecessary duplicate widgets, as multiple copies of similar visualizations can make the dashboard configuration difficult to manage and may contribute to unexpected behavior.
Once the required List View widgets are created and configured, add them to the existing dashboard or create a new dashboard based on the reporting requirement.
After implementation, validate the widgets by checking the filters, data displayed, dashboard interactions, and overall behavior. Once the new configuration is confirmed to be working correctly, remove any unnecessary duplicate widgets.
Following this approach will provide a cleaner dashboard configuration, simplify maintenance, and help avoid issues associated with duplicated List View visualizations.
