Forum Discussion

Frequent Visitor

7 years ago

Update Shared Datasouce for Report using PowerShell

Hello, We are in the process of migrating from SSRS to PBI-RS and have been testing reports in DEV using DEV Datasources. We have over 300 reports, that we need to switch to Production Datasourc...

Icon for Super User rank

Super User

6 years ago

If you want to point to a different shared data source you need to use the Set-RsDataSourceReference cmdlet

New Member

6 years ago

Thank you for the quick response. After reading through the help file for Set-RsDataSourceReference, the examples don't appear to align with my goal.

I ended up picking apart the function "Set-RsItemDataSource' and grabbing the last section.

https://imgur.com/Y3B2OE6

This ended up working and set my data source correctly.

My goal was to set the report data source to this. Does this look sane?

https://imgur.com/pSvkzTI

Thanks!

Eric

d_gosbell
Super User
6 years ago
erico wrote:

This ended up working and set my data source correctly.

If you figured out a script that works for you then that's great. If you are getting the result that you desire then that is probably proof in itself. I'm not sure how else you would measure the sanity of this 🙂
- erico
  New Member
  6 years ago
  Hi d_gosbell,
  
  Maybe "safe" is a better word lol. The section of the function I took is different than your recommendation. My concern is about the downstream effects, despite its immediate success.
  
  Your recommendation sets the DataSource like this...
  $Proxy.SetItemReferences($item, @($dataSourceReference))
  
  I set the DataSource like this...
  $rsProxy.SetItemDataSources($rsItem, $newDataSource)
  
  Thanks,
  Eric
  - d_gosbell
    Super User
    6 years ago
    erico wrote:
    
    Maybe "safe" is a better word lol. The section of the function I took is different than your recommendation. My concern is about the downstream effects, despite its immediate success.
    
    Oh in terms of "safety" you should be very safe with calling api methods like this. I sometimes see people in this forum suggesting doing direct updates on the Report Server database and that is definitely unsafe. But the powershell commands go through the supported web api calls which have a bunch of validations and checks in place and should ensure that there are no unwanted downstream effects.