Power BI is turning 10! Tune in for a special live episode on July 24 with behind-the-scenes stories, product evolution highlights, and a sneak peek at what’s in store for the future.
Save the dateEnhance your career with this limited time 50% discount on Fabric and Power BI exams. Ends August 31st. Request your voucher.
Hi,
I'm using CI/CD with DevOps repository. I have my semantic model in the repository (import mode). The semantic model ingests data from a lakehouse in workspace_dev. Now, I've copied the semantic model to prod branch in git. What I have now in prod branch is a semantic model pointing to the lakehouse in workspace_dev, but I need the semantic model to point to the tables in lakehouse from workspace_prod. workspace_dev and workspace_prod both have an identical lakehouse with the same tables and schema (different data content), and the semantic model is created from that lakehouse. How can I edit the semantic model in prod to ingets data from lakehouse in workspace_prod? The measures, dimensions, relationships between tables, etc, have to be the same. Do I have to create the semantic model from the beginning? This has no sense.
Solved! Go to Solution.
Hi @amaaiia,
Here are the steps how you can update the connection string in your semantic model to point to the lakehouse in workspace_prod:
1. Open the semantic model file (.pbix) for the prod branch in Power BI Desktop.
2. Go to the Manage Connections dialog (usually under the Home tab). This will show you the data connections currently defined in the model.
3. Identify the connection that points to the lakehouse tables. It might have a name related to workspace_dev.
4. Depending on how the connection string is defined, you might be able to directly edit it within the Manage Connections dialog.
5. Alternatively, the connection string might be defined within the Power BI Desktop file itself (usually in XML format). In this case, you'll need to edit the file directly using a text editor.
6. Within the connection string, replace any occurrences of "workspace_dev" with "workspace_prod". Ensure you're editing the values specific to the server or database name used to connect to the lakehouse.
7. Save the changes to your .pbix file.
8. Refresh the data model in Power BI Desktop to test the connection to the workspace_prod lakehouse.
9. Once everything works as expected, you can commit your changes to the prod branch in your Git repository and deploy the updated semantic model to your Power BI service workspace_prod.
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
Happy to help!
@Shivu-2000 this is not a full fledge solution are we going to download all the rpeorts to convert the connection when we deploy from DEV to PROD??
No right.. Your answer just suffice 1or 2 reports if i have 150 reports am not going to follow this steps.
Let me know if you have better solution for this!
Thanks!
Hi @amaaiia,
Here are the steps how you can update the connection string in your semantic model to point to the lakehouse in workspace_prod:
1. Open the semantic model file (.pbix) for the prod branch in Power BI Desktop.
2. Go to the Manage Connections dialog (usually under the Home tab). This will show you the data connections currently defined in the model.
3. Identify the connection that points to the lakehouse tables. It might have a name related to workspace_dev.
4. Depending on how the connection string is defined, you might be able to directly edit it within the Manage Connections dialog.
5. Alternatively, the connection string might be defined within the Power BI Desktop file itself (usually in XML format). In this case, you'll need to edit the file directly using a text editor.
6. Within the connection string, replace any occurrences of "workspace_dev" with "workspace_prod". Ensure you're editing the values specific to the server or database name used to connect to the lakehouse.
7. Save the changes to your .pbix file.
8. Refresh the data model in Power BI Desktop to test the connection to the workspace_prod lakehouse.
9. Once everything works as expected, you can commit your changes to the prod branch in your Git repository and deploy the updated semantic model to your Power BI service workspace_prod.
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
Happy to help!
Check out the July 2025 Power BI update to learn about new features.
This is your chance to engage directly with the engineering team behind Fabric and Power BI. Share your experiences and shape the future.
User | Count |
---|---|
29 | |
19 | |
19 | |
13 | |
12 |