Power BI
New"Import" REST Api call doesn’t work when Importing PBI report consuming existing dataset and with cross tenant
Rishi Garg on 10 Jun 2019 20:40:57
"Import" REST Api call doesn’t work when Importing PBI report consuming existing dataset and importing with cross tenant account. I have already raised a MS Support ticket (119012526003971) but got response that its not possible at present and need to raise a new idea.
Scenario:
• Create Report in Dev Env.
o Create PBI report (e.g. mypbireport1.pbix) using Powerbi desktop and AAD account (e.g. abcdev@test.com), which is connecting to external Datasource and then publish to a workspace e.g. devws. It creates dataset in Powerbi service with name as mypbireport1. (we can use either PBI desktop or Powershell REST API call to publish this kind of report)
o Create another report under same WS i.e. devws and using same AAD account (i.e. abcdev@test.com), mypbireport2.pbix and select mypbireport1 as datasource, which is created by mypbireport1 report publish. (for this kind of report, we can use Powerbi Desktop or Powershell command New-PowerBIReport to publish this.
• Now we are moving to suppose staging env and need to use AAD credentials for staging (e.g. abcstag@test.com)
o Use Powershell REST API to move the report mypbireport1.pbix to Staging env in new workspace (e.g. stagws). It creates dataset in Powerbi service with name as mypbireport1.
o Success scenario – Use Powerbi Desktop to first change the datasource connecting to dataset mypbireport1 under stagws. Then Publish to same workspace.
o Failed scenarios 1: Use Powershell REST API to move the report mypbireport2.pbix to same workspace stagws and with same AAD account (abcstag@test.com). It gives Bad Request error.
o Failed scenarios 2: Use Powershell command New-PowerBIReport (as per suggestion by MS team) to move the report mypbireport2.pbix to same workspace and with same AAD account. It gives Bad Request error.