Different Data source credentials in each Workspace

[Anonymous]

I have the same set of reports deployed in 3 different Workspaces; Prod, Test, and Dev.

The datasource is on Azure so there is no Gateway involved.  Once deployed I point the reports to the Prod, Test and Dev databases using parameters that I have setup in the report, this works well.

I then go to change the Data source credentials in each Workspace so that they use different user account for each environment database for Prod, Test and Dev.  When I do this on one report it changes for all reports in all Workspaces.

Ideally I want different credentials for each environment which i expect should be straightforward, how can I achieve this?  am I doing something wrong?

thanks

Bruce

[TomMartens]

Hey @Anonymous ,

what type is your Azure data source, is it Azure SQL or Azure Analysis Services, or something different?

Can you please share some screenshots that show, where and how change the parameter values, making the reports point to the different databases.

Please also share some screenshots that show where and how you change the credentials.

Please share some screenshots that from the data lineage view showing that the reports are "really" pointing to the proper databases after changing the parameters.

All what you want works in deployment pipelines, so it should be working if you do this manually 🙂

Regards,

Tom

[Anonymous]

Here you go...

Parameters in DEV;

Lineage in DEV:

Parameters in PROD:

Lineage in PROD:

Changing Data Source Credentials:

thanks

Bruce

[TomMartens]

Hey @Anonymous ,

this looks weird. I will test this on Wednesday, when I have some more time.

So basically what you are saying, is that after changing the parameters of the report instances pointing to the dev and prd instance, and then changing the credentials to make sure that the prd report instance is able to retrieve data from the prd database, both report instances are pointing to the prd database, right?

Regards,

Tom

[Anonymous]

The DEV report is pointing to the DEV database and the PROD report is pointing to the PROD database., this part works fine as you can see from the lineage. The problem is they both are using the same credentials.  Luckliy I have an admin account that has access to both databases as a workaround, but I want to use the accounts that were created for this purpose.  The dev account has read access to dev, and the prod one has read access to prod.

[Anonymous]

Hi @Anonymous ,

So you have 3 databases and one admin account has both access to these databases? Do you have any other account?

Best Regards,

Jay

[Anonymous]

Yes the admin account has access to all 3 databases.  The 3 accounts setup for reporting on the 3 database only has access to one database each, which I'd expect is good practice and reduces the chances of reports pointing to the wrong environment by mistake.  there are other accounts for other purposes but I'd expect them all to have the same restriction.