Forum Discussion
When I need to create a dashboard from different workspaces!?
- 4 years ago
Hi. I'm sorry but you can't pin a visual from a report to a different workspace. The workspaces are built to relate their own components inside of it. You can relate them to a different one.
You might need to think again the distribution of your reports to check if the current way make sense or if you should get them together in single workspace.
Another way would be connecting a small new report to the datasets that can handle the visualizations you want to pin. Create that report in the main area with that single visual and pin it.
There is a third option creating a new dataset with the aggregated data for the dashboard. Then pin that report visuals.
I hope this helps,
Hi
I know it is a late reply but posting it in case you are still considering options.
You cannot pin across workspaces - but there is a workaround that will solve the problem: You can copy a dataset from one workspace to another. This creates a reference to the dataset (it is not an actual copy with a separate refresh etc.). Once copied, you can pin from the copied dataset. Note: the target workspace must be be migrated to a 'new experience' workspace.
Regards
This would actually be a good workaround for me. Could you explain how you create a referenced dataset? Google came up empty
Edit: Unless this is what you are referring to
https://learn.microsoft.com/en-us/power-bi/connect-data/service-datasets-across-workspaces
- sfog3 years agoAdvocate II
Hi
Correct, that's the link that explains how to copy and re-use a dataset across workspaces. If you cannot copy a dataset to a workspace, you may need to migrate the workspace (as it must be a new experience workspace).
Another option that is in preview is; getting data from Power BI datasets (Direct AS).
So my recommendation would be: if the copy-and-pin to dashboard works for you, go with that because it is quick and easy. If you realise you need cross filtering and the dashboard approach does not work, consider using DIrect AS qqueries (you need to activate this in preview options). ALthough in preview, it works well and I've been using it quite a bit.
I wrote a white paper on this eact issue a while ago, which descibes the problem, provides the options and recommendations. I will try and publish it later this week/over the weekend (although it will state the same as above - so will not be anything new for you).
Good luck!
- andy8083 years agoResolver I
Thank you for your post, can you supply the link to your article? The MS link above is not very helpful or informative enough. Thanks!