Hi,
We have a single SQL Azure database with a schema per customer and a SQL user per schema that has access only to that schema. We then have a DirectQuery embedded report per customer that is sourced by the customer's schema. In the old workspace collection model we would save an instance of the report pbix in Desktop, deploy it and then update the database connection string based on the appropriate schema/user via the powerbi cli. That worked great.
In the new PowerBI service model (app.powerbi.com) we are deploying the customer's pbix to a customer specific workspace and setting credentials on its dataset but finding that those credentials are flowing to datasets in other workspaces that use the connection to the same server/database. The net result is that a previously loadable report will stop working because it no longer has access to its schema - apparently because it's using the most recently saved credentials from another workspace.
Is it no longer possible to do what we were doing in the workspace collection days - have a dataset connection string that varied from others only by username/pwd? Is a connection string that references the same server/database somehow global across workspaces in the new PowerBI or are we just setting ours incorrectly? Thanks for any hints or advice.
Dave
