Forum Discussion
undefined
Thank you rohit1991
Hi, Manmitha
According to the documentation, the RDL tool is only responsible for the migration, not the data source settings, and if your report has a shared data source, the RDL migration tool will try to convert the shared data source to an embedded data source. Regardless of whether you have created a corresponding data source, you should specify the correct data source for your report:
Plan to migrate .rdl reports to Power BI - Power BI | Microsoft Learn
This is noted in the documentation, but of course you may encounter your situation when the RDL migration tool tries to create an embedded data source, due to a different environment. The tool was last updated in 2022. So there may be some incompatibility with your current environment.
Releases · microsoft/RdlMigration · GitHub
Best Regards
Jianpeng Li
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
Hi , hope this helps:
The issue arises because the RDL Migration Tool converts shared data sources to embedded ones, creating duplicates and breaking dataset references. To resolve:
Clean RDL Files:
- Open the converted RDL in Report Builder.
- Remove duplicate embedded data sources in the <DataSources> section and point all datasets to a single source.
Use Shared Data Sources:
- Create shared data sources in your Power BI Premium Workspace.
- Update the RDL to reference these shared sources.
Check Tool Settings:
- Disable embedded data source creation in the migration tool settings (if available).
Manually Repoint Datasets:
- After uploading, assign datasets in Power BI to correct shared data sources.
By aligning data sources in your workspace and the RDL, the upload should succeed.