Dashboard Deployment Issue

[Pradeep_C_M]

Hi @all
I deployed my Dashboard from Dev to QA in Power BI Service but the QA connection didn't show up in the Gateway and Cloud connection part what could be the issue? How to resolve it

I created the 2nd connection tried adding it manually but that too not showing up.

I'm the owner of the connection

How to fix this permanently?

[Pradeep_C_M]

Yes, I did the same way but the problem is It is not showing the connection I created explicitly for QA where other reports are working fine.

[v-aatheeque]

Hi @Pradeep_C_M 

Could you please share a screenshot of the Gateway and cloud connections section where the QA connection is expected to appear? Also, let us know if there are any error messages shown.

[Pradeep_C_M]

It should show Prod because it's now in Prod. But it's not showing.

[v-aatheeque]

Hi @Pradeep_C_M 
Could you please verify whether the Prod cloud connection is available and mapped under Gateway and cloud connections? If the required connection is not configured or mapped it may not appear in the deployment dropdown.

[v-aatheeque]

Hi @Pradeep_C_M 

We wanted to follow up to check if you’ve had an opportunity to review the previous responses. If you require further assistance, please don’t hesitate to let us know.

[andrewsommer]

Issues like this with deployment pipelines are pretty common.  In general, I think the deployment pipelines are more trouble than they are worth.

With that said, start by checking if the data source has a string mismatch.  The semantic model settings section only lists gateways/connections that have matching data source definitions for every source used in the model. The server and database name need to match exactly between what's defined in the connection and what's embedded in the semantic model.

When you deployed Dev to QA, the semantic model still carries the Dev datasource string baked into it. If your QA connection was built pointing at a different server/database name or path, Power BI won't match them.

The deployment process replicates the metadata of reports and semantic models, but the structure is replicated, but connections are not automatically re-bound. You need to manually map the QA semantic model to the correct connection after each deployment.