The ultimate Fabric, Power BI, SQL, and AI community-led learning event. Save €200 with code FABCOMM.
Get registeredEnhance your career with this limited time 50% discount on Fabric and Power BI exams. Ends August 31st. Request your voucher.
Hi gang,
I have a weird one... My company asked me to make some reports and gave me a direct connection to a source SQL database that I used to create my local dataset.
Interesting request, they are asking us to separate our reports from our datasets and they want to take the dataset from my PBIX file and publish it in a company (PowerBI/Sharepoint?) workspace, then have me re-connect my reports to this new data source, which should presumably be identical to the one I am working on locally.
Any recommendations on how to navigate this change with minimal reconnection frustration?
Items that I'm thinking about:
THANKS
Solved! Go to Solution.
If you already have reports, you can copy all visuals to a new report that is already connected to the dataset and they will all work.
DAX is for Analysis. Power Query is for Data Modeling
Proud to be a Super User!
MCSA: BI ReportingI have created a powershell script that creates a new PBIX file with just the reports in it from a pbix that is the dataset. I have found it a lot easier than to do this whole process manually. https://github.com/rajrao/mypublicnotes/blob/master/PowerBi/ConvertDatasetPbixToReportsOnly.ps1
If you already have reports, you can copy all visuals to a new report that is already connected to the dataset and they will all work.
DAX is for Analysis. Power Query is for Data Modeling
Proud to be a Super User!
MCSA: BI ReportingThis worked perfectly - I tested it out and VOILA! Golden.
Thanks again, @edhans - you make my life less stressful 🤓
Great. This also has another benefit. You can work on the data model and someone else can work on the visual report since they are separate PBIX files.
DAX is for Analysis. Power Query is for Data Modeling
Proud to be a Super User!
MCSA: BI Reporting