This is best Fabric, Power BI, SQL and AI community event. How do we know? The last event sold out! Save €200 with code FABCMTY200.
Register nowA new Data Days event is coming soon! This time we’re going bigger than ever. Fabric, Power BI, SQL, AI and more. Don't miss out.
Hello,
I'm new to Microsoft Fabric and I need some help.
I created a semantic model based on a data warehouse located in Workspace DEV. When I deploy the semantic model to another workspace, for example Workspace TEST, it still remains attached to the original Workspace DEV.
How can I change the data source of the semantic model so that it points to the data lake in the test workspace? I couldn't find any solution so far.
Solved! Go to Solution.
Hello,
The solution founded and tested is to import the semantic model and modify the following line in the expressions.tmdl file located under yourmodel.SemanticModel\definition: powerquery Copy Edit database = Sql.Database("ciblecnx.datawarehouse.fabric.microsoft.com", "ciblecnx")
Procedure:
Open your semantic model in Power BI Desktop (latest version).
After that, choose the "Modification" option (in Power BI Desktop).
Export the project using Project Power BI (PBI Project format)
Choose the export path where your project will be saved (this will generate a folder structure with .pbip and SemanticModel folders).
After that, you should access:
yourmodel\SemanticModel\definition\expressions.tmdl
And change the line powerquery Copy code database = Sql.Database("target_server", "target_database") in the expressions.tmdl file with your target database information. After making this change, save and close the file. Then, close all open Power BI projects. Reopen the .pbip file — you will see an interface where you can: Choose the target workspace Set a new semantic model name
best regards
Rida BENBOUZIANE
Hello,
The solution founded and tested is to import the semantic model and modify the following line in the expressions.tmdl file located under yourmodel.SemanticModel\definition: powerquery Copy Edit database = Sql.Database("ciblecnx.datawarehouse.fabric.microsoft.com", "ciblecnx")
Procedure:
Open your semantic model in Power BI Desktop (latest version).
After that, choose the "Modification" option (in Power BI Desktop).
Export the project using Project Power BI (PBI Project format)
Choose the export path where your project will be saved (this will generate a folder structure with .pbip and SemanticModel folders).
After that, you should access:
yourmodel\SemanticModel\definition\expressions.tmdl
And change the line powerquery Copy code database = Sql.Database("target_server", "target_database") in the expressions.tmdl file with your target database information. After making this change, save and close the file. Then, close all open Power BI projects. Reopen the .pbip file — you will see an interface where you can: Choose the target workspace Set a new semantic model name
best regards
Rida BENBOUZIANE
Hi @ridabenbouziane ,
May I ask if you have resolved this issue? If so, please mark the helpful reply and accept it as the solution. This will be helpful for other community members who have similar problems to solve it faster.
Thank you.
Hi @ridabenbouziane ,
I wanted to check if you had the opportunity to review the information provided. Please feel free to contact us if you have any further questions. If my response has addressed your query, please accept it as a solution and give a 'Kudos' so other members can easily find it.
Thank you.
Hi @ridabenbouziane ,
Thanks for reaching out to the Microsoft fabric community forum.
In Microsoft Fabric, when you deploy a semantic model from one workspace to another using deployment pipelines (e.g., from DEV to TEST), the data source doesn’t update automatically, it stays connected to the original source in DEV.
To point the semantic model in TEST to the correct data source, you’ll need to manually update it. If the model was created using Power BI Desktop, open the file, go to Data Source Settings, change the source to the TEST environment, and republish it. If it was created directly in Fabric, you'll need to recreate it in TEST with the correct source.
For more detailed information, please refer to the documentation provided by @lbendlin
I hope this will resolve your issue, if you need any further assistance, feel free to reach out.
If this post helps, then please give us Kudos and consider Accept it as a solution to help the other members find it more quickly.
Thankyou.
hello @Anonymous
Thank you for your response. Unfortunately, I created it directly in Fabric, so I think I am forced to recreate it in TEST mode.
Hi @ridabenbouziane ,
Thank you for the confirmation.
You're right, currently semantic models created directly in Microsoft Fabric do not support data source redirection between workspaces via deployment pipelines. Therefore, the only available option is to recreate the model in the TEST workspace and connect it to the appropriate data source.
This is a known limitation, for updates on this capability, please refer to the Microsoft Fabric release plan.
If this post helps, then please give us Kudos and consider Accept it as a solution to help the other members find it more quickly.
Thankyou.
Hi @ridabenbouziane ,
I wanted to check if you had the opportunity to review the information provided. Please feel free to contact us if you have any further questions. If my response has addressed your query, please accept it as a solution and give a 'Kudos' so other members can easily find it.
Thank you.
Hello,
I think I’ve found something that might allow us to make this change. I’m currently testing it by importing the semantic model into the latest version of Power BI Desktop. exported it pbip
Once inside, you can go to:
yourmodel.SemanticModel\definition\expressions.tmdl
I’m still testing this approach to make sure it works correctly.
Best regards,
Are these workspaces part of a Deployment Pipeline?
Yes, I have a deployment pipeline with Workspace DEV linked to Workspace TEST. However, after testing by detaching them, the semantic model is still attached to the data warehouse from Workspace DEV.
This document has the latest scope on what is and isn't configurable.
The Microsoft Fabric deployment pipelines process - Microsoft Fabric | Microsoft Learn
Check out the June 2026 Fabric update to learn about new features.
Sign up to receive a private message when registration opens and key events begin.
| User | Count |
|---|---|
| 18 | |
| 9 | |
| 7 | |
| 7 | |
| 7 |
| User | Count |
|---|---|
| 21 | |
| 17 | |
| 16 | |
| 11 | |
| 11 |