ODBC Connection String Properties Static Between Reports?

[Anonymous]

I have two reports, one of which is a variant that is to access a different database (a different company code specifically). The two reports are identical otherwise.

I've successfully constructed the second report, entering the credential connection string properties Company=XXX, and it works, but suprisingly, that string sticks to every single report that I've built using that data source in Power BI! So, when I switch it back on the other reports, it reverts my variant report to the company code I did not intend for it to use.

Can I get this string only to be attached to this particular report, or do I need to construct a whole new ODBC datasource with this new connection string?

[Anonymous · Accepted solution]

I've solved this by instead adding the connecton string property at the query level in the Power Query editor.

The second step is to make sure to add this as a new data source in the data gateway (if you wish to auto refresh).

Thanks @Greg_Deckler for the response as I started some research on using parameters too. A whole new area for me to learn!

[Greg_Deckler]

@Anonymous I would construct your connection string using a query parameter for the unique portion of the connection string.