Datamodel should list all dependent dashboards not just where this is the primary model
See pictures.
Or go: 1. Open datamodel. 2. Click the Dashboards dropdown. 3. Click Open Dashboard.
It lists dependent dashboards. But it includes only dashboards where this data model is the "primary" data source. That is dangerous. It made me think that "No dashboards are available for this model" and I nearly deleted the model.
The list should show all dependent dashboards. I will use the API to check dependencies in future.
I responded to another one of your posts with the same solution, but I wanted to share here as well!
I see that a solution has been provided below to use the dashboards API endpoint to get the list of dashboards associated with a data model. And while that definitly will work, it does create a bit more overhead for you.
The new Asset Auditor plugin can help get you this information, but also allows you to do much more with it. On our Dashboards dashboard, you can see exactly which dashboards are associated with which data models. Dashboards are linked so that you can navigate directly to those dashboards.
Additionally, the Asset Auditor provides visibility into both Empty and Unused data models. You can have higher confidence when removing data assets that may have an unintended impact on downstream assets.
And because the Asset Auditor is built using Sisense native charts and features, you can create new charts or augment the provided charts to show the data that would be most helpful to you.
Hopefully, this provides another option for you to explore that can go beyond just a point solution for this use case. Again, feel free to check out the blog post, our documentation, or reach out if you want some more information.
Tim Glad to hear the Dependencies button (or API) provides the information you need. I see your point about the UI. Your idea is definitely valid, and the product team can take a look at it. Thanks for sharing your perspective
Thanks AssafHanina, I didn't see the Dependencies button. That (or the API) provides the information I need.
I still think UI makes it likely other people will make the same mistake as me. And why bother having a "Dependencies" button and a "Dashboards" button when they're used for the same thing? I think you should replace the "Dashboards" drop-down with the output the of the "Dependencies" button.
