Don't miss your chance to take the Fabric Data Engineer (DP-600) exam for FREE! Find out how by attending the DP-600 session on April 23rd (pacific time), live or on-demand.
Learn moreNext up in the FabCon + SQLCon recap series: The roadmap for Microsoft SQL and Maximizing Developer experiences in Fabric. All sessions are available on-demand after the live show. Register now
Hello Community,
I am trying to switch my production env so that files are hosted in SharePoint and uploaded from SP straight to Service.
1)
If I just download the file, upload to SharePoint and upload it to the service from there I get duplicate model/report with the same name? I didn't think this was possible in PBI Service.
I suspected this was happening because the original had been published in the "normal" manner but see 2:
2)
Even if the file comes from SharePoint and I then re-upload it I get a second version of the same file with the same name.
3) When I upload a .pbix from SharePoint a dashboard is created - apparantly by me - with nothing in it but a link to the report?
Is uploading from SP really this different from uploading from PBI or am I experincing some kind of error here?
Solved! Go to Solution.
Names are generally not relevant, for the majority of cases the GUID controls the object. (One notable exception is the XMLA endpoint which uses the workspace name, with predictably hilarious results when two workspaces happen to have the same name).
Once you have "imported" the pbix to the workspace from the sharepoint this will create a virtual connection. Your only action required from now on is to work on the pbix on the sharepoint/onedrive. Every time you save that a new version will be created (assuming you have versioning enabled on that document library), and the meta data changes will be synchronized with the workspace "automatically".
Names are generally not relevant, for the majority of cases the GUID controls the object. (One notable exception is the XMLA endpoint which uses the workspace name, with predictably hilarious results when two workspaces happen to have the same name).
Once you have "imported" the pbix to the workspace from the sharepoint this will create a virtual connection. Your only action required from now on is to work on the pbix on the sharepoint/onedrive. Every time you save that a new version will be created (assuming you have versioning enabled on that document library), and the meta data changes will be synchronized with the workspace "automatically".
If you have recently started exploring Fabric, we'd love to hear how it's going. Your feedback can help with product improvements.
A new Power BI DataViz World Championship is coming this June! Don't miss out on submitting your entry.
Experience the highlights from FabCon & SQLCon, available live and on-demand starting April 14th.
| User | Count |
|---|---|
| 11 | |
| 10 | |
| 9 | |
| 8 | |
| 8 |