RAKESHNUGURI - Hey everyone 👋We’ve had some c...
Hey everyone 
We raised a support ticket recently regarding drilldown capabilities in embedded visualizations, and Support suggested we reach out here to the Embed team for deeper guidance and examples.
We’ve had some client requests asking if they can drill down into embedded visualizations for more insights.
We started exploring callback custom actions, and we’ve managed to redirect users to another dashboard with it. However, we’ve hit a few limitations:
We have to extract a specific column from the clicked row and pass that as a filter — this restricts users from choosing which column they want to filter by.
We have to hard-code the filter column, and also pass visualizationId and liveboardId to redirect — this gets messy when trying to make the setup generic.
We'd potentially need to create multiple custom actions mapped to different visualizations — not ideal.
As an alternative, we’re considering URL-based custom actions.
Does anyone have a working example of URL custom actions (Action Type = URL) where you can pass multiple filters dynamically?
The goal is to avoid heavy manual configuration in our app.
Also, separate question:
If we enable drilldown functionality, is there a way to restrict which columns users can drill down by?
For example: for Skills dashboard, we only want them to drill down by Skill, and not by things like User ID, Assessment Key, or Tenant Name.
Any help or insights would be super appreciated — thanks in advance!
We raised a support ticket recently regarding drilldown capabilities in embedded visualizations, and Support suggested we reach out here to the Embed team for deeper guidance and examples.
We’ve had some client requests asking if they can drill down into embedded visualizations for more insights.
We started exploring callback custom actions, and we’ve managed to redirect users to another dashboard with it. However, we’ve hit a few limitations:
We have to extract a specific column from the clicked row and pass that as a filter — this restricts users from choosing which column they want to filter by.
We have to hard-code the filter column, and also pass visualizationId and liveboardId to redirect — this gets messy when trying to make the setup generic.
We'd potentially need to create multiple custom actions mapped to different visualizations — not ideal.
As an alternative, we’re considering URL-based custom actions.
Does anyone have a working example of URL custom actions (Action Type = URL) where you can pass multiple filters dynamically?The goal is to avoid heavy manual configuration in our app.
Also, separate question:
If we enable drilldown functionality, is there a way to restrict which columns users can drill down by?
For example: for Skills dashboard, we only want them to drill down by Skill, and not by things like User ID, Assessment Key, or Tenant Name.
Any help or insights would be super appreciated — thanks in advance!
