Register now to learn Fabric in free live sessions led by the best Microsoft experts. From Apr 16 to May 9, in English and Spanish.
We have currently a project, that should deliver several PBIX-Files to different customers.
Every PBIX-File should access the same SQL Azure Database, but should use different SQL Login-Credentials (since not every customer should be able to access all database objects). If we now wanna test this on our local environment, and create these PBIX-Files with different SQL Logins, it always overwrites the SQL Logins of the global Datasource. This is indeed annoying, but can be worked around by just entering the logins again and again before publishing.
The real problem shows up when we publish these PBIX-Files to Power BI Web and try a scheduled refresh of multiple datasets:
Since the SQL Login gets always overwritten as soon as you publish a new PBIX-File, it kind of uses a random SQL Login, so we cannot guarantee to provide the correct data to the original files.
Our question now is if it's really fully intended to always overwrite the logins of a global Datasource, even in different, shared workspaces or will there be any solution in the future to store the logins with the files or provide a section to manage the Datasources properly (maybe analog the SSRS-Datasources)?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.