No SetAllConnections support for ImportMode a show stopper!

[trevorgermain]

As an enterprise SAAS organization, we need to automate all of our deployment processes. I've got a full deployment scenario scripted, but it fails on SetAllConnections due to the fact that the report(s) are import mode. We need this support ASAP!

[v-ljerr-msft]

Hi @trevorgermain,

For anyone who also need this feature, please vote the idea and add your comments here to improve Power BI on this feature. 

Regards

[nimrod]

Try this one- https://msdn.microsoft.com/en-us/library/mt814715.aspx

It's newer and supports import mode for few datasources.

[trevorgermain]

The request allows you to change server and database. How do you also update the credentials for the source? Obviously, if you are changing to a different environment (e.g. staging to production), there will be a different set of credentials.

{
      "connectionDetails":
      {
        "server": "new-Sql-Server.com",
        "database": "new-Sql-Database"
      },
      "datasourceSelector":
      {        
        "datasourceType": "Sql",
        "connectionDetails": 
        {
          "server":"My-Sql-Server",
          "database":"My-Sql-Database"
        }
      }
    }

[trevorgermain]

What was nice about SetAllConnections was that I could set all connections to a specific connection string. My scenario:

- I develop a report, connecting to a local copy of a database. (e.g. instance = server1, db = DataWarehouse

- My teammate develops a different report, connecting to a local copy of his database. (e.g. server2, db = DW

With SetAllConnections, I can write a deployment that imports both reports from source control, and updates both reports to connect to production (e.g. instance = azureserver\production db = DataWarehouse).

With UpdateDatasource, I need to explicitly know that the "source" database to update is server1; DataWarehouse and server2; DW. This removes the ability to have a generic deployment script.

[nimrod]

Use 'Set credentials'