Forum Discussion

Piquet65's avatar
Piquet65
Frequent Visitor
3 years ago

Is it just me, or does the inability for Power BI Report Server deployments to modify the connection string without modifying the Power BI report being deployed each time seem like a significant functional hole in the platform?

I'm sure most organisations would have multiple PBIRS environments up-stream from PRODUCTION (i.e. DEV, TEST, etc.) to deploy to after appropriate testing has been completed, & it seems wrong / high risk to have to be opening up and editing the code in a deployment asset each time it needs to progress to a downstream environment.

This requirement to modify the PBIX for each environment has been reported several years ago now and is still a requirement, suggesting that it's not considered an issue worth worrying about by the Power BI team @ Microsoft. 

What point am I missing here? i.e. Why isn't this considered a significant issue and hence already addressed since 2018?

Are there any plans to address it? Or do we need to struggle along modifying each PBIX as we deploy to a downstream environment and/or look at developing our own PBIRS report deployment tool?

Simply retaining the data source connection details when a PBIX report REPLACES an existing report on PBIRS would be a great step forward/improvement. Currently it seems that automating Power BI report deployments wired up for downstream envuironments is not a feasible option.

 

Am I right, or am I missing something?

 

Piquet