Refresh fails after deployment of dataflow through Power BI deployment pipeline

[Anonymous]

Hi,

Our environment makes use of a datagateway to the data source configured with a user principal. We use dataflows (gen1) to connect to the source and get data in the service. 
A data source rule is set on the dataflow in the deployment pipelines, changing the connection from dev to test when deployed from dev workspace to test workspace.

In the dev workspace (before deployment) we do not encouter issues with refreshing the dataflows. However, after deployment to the test workspace the dataflow fails on the first refresh because of credentials. The test environment is connected over the same gateway as the dev environment. 

When opening the dataflow the error states: Credentials are required to connect to the SQL source. (source string). It asks you to manually connect again after deployment before being able to refresh the data.

After manually connecting in the dataflow (power query) using the same gateway (user principal configured) it fixes the error and refreshes.

I can't figure out why this manual reconnection is needed after deployment. If anyone has some clues please shoot, Thanks

[suparnababu8]

Hi @Anyonumus

I agree with @GilbertQ comments
The issue you’re encountering with the dataflow failing to refresh after deployment is likely due to the credentials not being automatically updated when the data source changes from dev to test. 

Follow below steps
- Update Credentials Post-Deployment

- Use Parameterized Connections

- Automate Credential Updates

Need additional info visit this https://learn.microsoft.com/en-us/power-bi/connect-data/refresh-troubleshooting-refresh-scenarios 

[GilbertQ · Accepted solution]

Hi there

The reason that this is happening is because when you change the data source, you. also then need to update the credentials for that new data source. So while the deployment pipelines are moving it to a different data source, it doesn't automatically update the credentials for that data source. You would need to do this every time there's a deployment change as far as I am aware.