Find everything you need to get certified on Fabric—skills challenges, live sessions, exam prep, role guidance, and more.
Get startedGrow your Fabric skills and prepare for the DP-600 certification exam by completing the latest Microsoft Fabric challenge.
Hello.
I am beginning to work with Power BI pro, and my colleagues in Office 365.
What I want is to separate the action of publishing in two layers: report and dataset. I have done this:
1. Publish a new report from desktop to a PWbi pro apps workspace.
2. Then I have a report and a dataset with the same name. I do not need the report, because what I want is to publish just the dataset.
3. Done this, I want my colleagues to connect to this dataset, and create new reports. They can do it in both places: Desktop, and service, but I have the useless report of the initial published one.
A homemade solution has been to publish it the way I have described, and then delete the report. The problem is that each time I change the data model (including a new measure, for example), I have to delete the report again when I publish.
I have been looking for a solution for this subject this morning without any success. This is why I generated this message.
Thanks in advance.
Solved! Go to Solution.
Once you publish .pbix from Power BI Desktop, both dataset and report will be uploaded onto Power BI Service. It's not possible to publish dataset only from Power BI Desktop. You can only delete the uploaded report and create your own one.
Regards,
Once you publish .pbix from Power BI Desktop, both dataset and report will be uploaded onto Power BI Service. It's not possible to publish dataset only from Power BI Desktop. You can only delete the uploaded report and create your own one.
Regards,
Is publishing of dataset only likely to be added as a feature? This would be supportive of common productive development patterns (basically separating source from presentation is in general a good principle, and in particular allows us to do things like develop slightly more general data sets that analysts can then use quickly to put together adhoc reports).
We are working this way and using the "publish then delete" approach. To avoid cluttering the workspaces we have to rely on hard-to-enforce naming conventions and periodic clean-ups.
Hi,
I created an improvement idea which you can find here. I hope it is exactly what you mean, such feature would help us all!
Join the community in Stockholm for expert Microsoft Fabric learning including a very exciting keynote from Arun Ulag, Corporate Vice President, Azure Data.
Ask questions in Eventhouse and KQL, Eventstream, and Reflex.