Power BI is turning 10! Tune in for a special live episode on July 24 with behind-the-scenes stories, product evolution highlights, and a sneak peek at what’s in store for the future.
Save the dateEnhance your career with this limited time 50% discount on Fabric and Power BI exams. Ends August 31st. Request your voucher.
Hello,
Is there a checklist or standard set of criteria to use when changing the data source of a report from SharePoint Lists to Dataverse tables?
The optimist in me hopes that its just a case of changing the data source URL but I imagine its going to be more complex given the differences between Dataverse and SPOL.
Will the existing queries require significant editing or might it be better to start from scratch and replicate the reports?
Thank you.
Solved! Go to Solution.
Hi @Class66Loco,
Thanks for reaching out to the Microsoft Fabric Forum Community.
Migrating a Power BI report from SharePoint Lists to Dataverse isn't just changing the data source URL it involves key differences in structure, relationships, and data types.
Checklist Key Points:
Check schema: Dataverse uses strict types and relationships; SPOL is flat and flexible.
Update queries: Power Query steps may need adjustments, especially for lookups or nested fields.
Rebuild relationships: Dataverse supports native relationships you may need to define.
Adjust DAX: Revisit measures and calculated columns using SharePoint-specific fields.
Test visuals and performance: Validate data accuracy and performance in the new setup.
It's usually not worth rebuilding from scratch unless the original report is messy or outdated.
If this helped, please mark the response as the accepted solution and give it a thumbs-up so others can benefit too.
Best regards,
Prasanna Kumar
Hi @Class66Loco,
Just a gentle reminder has your issue been resolved? If so, we’d be grateful if you could mark the solution that worked as Accepted Solution, or feel free to share your own if you found a different fix.
This not only closes the loop on your query but also helps others in the community solve similar issues faster.
Thank you for your time and feedback!
Best,
Prasanna Kumar
Hi @Class66Loco,
Just a gentle reminder has your issue been resolved? If so, we’d be grateful if you could mark the solution that worked as Accepted Solution, or feel free to share your own if you found a different fix.
This not only closes the loop on your query but also helps others in the community solve similar issues faster.
Thank you for your time and feedback!
Best,
Prasanna Kumar
Hi @Class66Loco,
We wanted to kindly check in to see if everything is working as expected after trying the suggested solution. If there’s anything else we can assist with, please don’t hesitate to ask.
If the issue is resolved, we’d appreciate it if you could mark the helpful reply as Accepted Solution it helps others who might face a similar issue.
Warm regards,
Prasanna Kumar
Hi @Class66Loco,
Just following up to see if the solution provided was helpful in resolving your issue. Please feel free to let us know if you need any further assistance.
If the response addressed your query, kindly mark it as Accepted Solution and click Yes if you found it helpful this will benefit others in the community as well.
Best regards,
Prasanna Kumar
Hi @Class66Loco,
Thanks for reaching out to the Microsoft Fabric Forum Community.
Migrating a Power BI report from SharePoint Lists to Dataverse isn't just changing the data source URL it involves key differences in structure, relationships, and data types.
Checklist Key Points:
Check schema: Dataverse uses strict types and relationships; SPOL is flat and flexible.
Update queries: Power Query steps may need adjustments, especially for lookups or nested fields.
Rebuild relationships: Dataverse supports native relationships you may need to define.
Adjust DAX: Revisit measures and calculated columns using SharePoint-specific fields.
Test visuals and performance: Validate data accuracy and performance in the new setup.
It's usually not worth rebuilding from scratch unless the original report is messy or outdated.
If this helped, please mark the response as the accepted solution and give it a thumbs-up so others can benefit too.
Best regards,
Prasanna Kumar
Check out the July 2025 Power BI update to learn about new features.
User | Count |
---|---|
73 | |
71 | |
38 | |
29 | |
28 |
User | Count |
---|---|
99 | |
88 | |
62 | |
42 | |
39 |