Hey, we have encountered an issue where a specific visualization functions correctly on the parent dashboard but fails to do so on one of its child dashboards. All other visualizations within the child dashboard operate as expected. Additionally, the Logical Data Model (LDM) shows no errors, and the WDF appears to be functioning as intended. Below is the error message we are receiving. Can we investigate somehow the cause of this error?

Hi Evangelos, off the top of my head this sounds like it may perhaps relate to a parent and child dashboard and how filters are applied. Filters from the parent dashboard can cascade to child dashboards, and this might be causing the visualization to behave differently. From the dashboard, are you able to open the visualisation and it works in the “Analyze” tab and does it work correctly there? If yes, I would like to suggest to inspect filters on both dashboards: Ensure that the filters applied on the child dashboard are not conflicting with the data expected by the visualization. If the above doesn’t help, can you please provide us with the related Trace ID so we can check our logs for you?

Hi @Michael Ullock and thank you for your reply. From the parent dashboard, I'm able to open the vizualization properly. On the child dashboard, since you can't edit it, I couldn't check the vizualization, but I managed to build one new from scratch and it also works as expected. Also on the child dashboard there is another vizualization with the same datasource that behaves as expected. So, I'm not entirely sure where the problem lies. I don't have a error trace id as I cannot edit the child dashboard but I can provide you with the following ids: * parent dashboard id:

prod.master

* parent dashboard vizualization:

viz.anpr.hourly.visitor.sessions.per.payment.type

* child dashboard id:

prod.sme

* test vizualization in child dashboard:

6983e1bd-994a-4478-9ce2-85a2b702fdc4

Hi Evangelos, I've reached out to you via an internal ticket. Please check your email.

Hi @Moises Morales, thanks for the reply. My reply can be found at the internal ticket 🙂