ODBC deployment rules

[beag]

Hi,

We have two environments in Datasphere (development and production), and we connect to them using an ODBC connector.

I would like to to connect to the development environment and change the connection to the production one when the semantic model is deployed to the production workspace using the deployment pipelines. I can't seem to implement deployment rules for this semantic model though. Is there a way to achieve this change of enviroment when my data source connector is ODBC?

[beag]

The solution worked, the environment is changed in the different stages of the pipeline. The problem I am facing now are the database credentials, as they are different betwween environments and I am not able to update them in the semantic model setting or add a rule for changing them in the pipeline, can't find a way to parametrice them. 

Is this something that can be solved, or maybe can be taken care of when using gateway connections? We don't have these yet in place, but shpuld be implemented soon too.

[v-saisrao-msft]

Hi @beag,

Please check the below references which describe a similar issue and may help resolve your case

Solved: Change SQL database credentials in Power BI deploy... - Microsoft Fabric Community

Create deployment rules for Fabric's ALM - Microsoft Fabric | Microsoft Learn

Thank you.

[v-saisrao-msft]

Hi @beag,

Have you had a chance to review the solution we shared by @grazitti_sapna? If the issue persists, feel free to reply so we can help further.

Thank you.

[v-saisrao-msft]

Hi @beag,

Have you had a chance to review the solution we shared by @grazitti_sapna? If the issue persists, feel free to reply so we can help further.

Thank you.

[grazitti_sapna · Accepted solution]

Hi @beag 

When using ODBC connections in Power BI Datasphere, deployment pipelines don’t automatically switch connection strings unless they are set up as parameters in your semantic model or dataset.

If your ODBC DSN or connection string is hardcoded, deployment pipelines can’t change it directly.

Here’s what you can do:

• Use parameters in your dataset/semantic model for parts of the ODBC connection (like server name) so deployment pipelines can update these during deployment.
• Manage separate ODBC DSNs for dev and prod on your gateway and configure deployment pipelines to use the correct gateway connection.
• If parameters aren’t possible, manually update the connection string after deployment.

In short, to automate switching, parameterize connection info or use gateway DSNs mapped correctly per environment. Do let us know if it helps.

🌟 I hope this solution helps you unlock your Power BI potential! If you found it helpful, click 'Mark as Solution' to guide others toward the answers they need.

💡 Love the effort? Drop the kudos! Your appreciation fuels community spirit and innovation.

🎖 As a proud SuperUser and Microsoft Partner, we’re here to empower your data journey and the Power BI Community at large.

🔗 Curious to explore more? [Discover here].

Let’s keep building smarter solutions together!