Forum Discussion
Issue linking Dashboard tile when underlying Report is removed and re-linked
Hi,
In our DevOps pipeline we have steps for updating a Report which are as follows:
- Delete existing Report with same name
- Publish updated Report
- Rebind newly published report to Dataset
This works fine but when we try to re-map Dashboard Tiles to these Reports then the drill-through to underlying Report is broken.
I am trying to find a solution that will allow the Dashboard tile to correctly map to the new Report in the existing workspace so that when we update a Report, and then re-map Dashboard tile, that it will allow us to click on tile and be brought to the linked Report.
Is this posible via the API, or through some kind of configuration on the Dashboard?
Thanks,
Conor
This is beacause when you delete the report and publish again the Report ID gets updated and the tile in dashboard is linked with the old report id
There is no API to add tile in dashboad as of now, only way is do it manually
you can add your idea on https://ideas.fabric.microsoft.com/?forum=2d80fd4a-16cb-4189-896b-e0dac5e08b41
2 Replies
- arvindsingh802
Community Champion
This is beacause when you delete the report and publish again the Report ID gets updated and the tile in dashboard is linked with the old report id
There is no API to add tile in dashboad as of now, only way is do it manually
you can add your idea on https://ideas.fabric.microsoft.com/?forum=2d80fd4a-16cb-4189-896b-e0dac5e08b41 Hi,
Yes, thanks, that is what is happening but we do currently use API to clone a working dashboard from another workspace and remap the tiles to the new Report GUIDs. The only thing missing is the link to the underlying report when a user clicks on the dashboard tile.
Manually adding tiles is not an option unfortunately as we have over 25 production workspaces that need Dashboards deployed to them each time Reports are updated, so this just wouldn't be feasible.
That link appears to be broken for me as well, sorry. If I can access it I will suggest they make the API more usable for these kind of scenarios.
Thanks for your help, have a nice day.
