Forum Discussion

Conlyn's avatar
Conlyn
Advocate I
3 years ago

Unwanted data source created when publishing rdl report

I am using the MicrosoftPowerBIMgmt powershell module to push rdl reports to workspaces. I then want to update the report data source to map to the proper data source that already exists in our on pr...
Need Help
tackytechtom's avatar
tackytechtom
Most Valuable Professional
3 years ago

Hi Conlyn ,

 

I actually had some issues with data sources as well when I labbed with the TOM library. I, however, was only using it towards Power BI datasets, so this one still might be a long shot: Have a look into the following resources:

 

https://www.tackytech.blog/how-to-automate-the-management-of-custom-partitions-for-power-bi-datasets/#appendix

https://powerbi.microsoft.com/en-us/blog/using-xmla-endpoints-to-change-data-sources-in-a-power-bi-dataset/

 

Essentially, it had to do with the alias of the data source. Once again, this one yields for Power BI datasets but it might point you into the right direction anyway. 

 

Curious to see how you will solve it, though! Hopfully, you can keep us posted in here!

 

/Tom
https://www.tackytech.blog/
https://www.instagram.com/tackytechtom/

Conlyn's avatar
Conlyn
Advocate I
3 years ago

Hi tackytechtom,

 

Thanks for the reply, but unfortunately there doesn't seem to be (or I can't find) a way to progamatically bind a paginated (.rdl) report to a Gateway Datasource. I tried changing the Datasource Name in my .rdl to match the Gateway Datasource Name, but it still created a new one named {"server":"[servername]","database":"[databasename]"} instead of finding the exising one that matched.

 

-Conlyn