Forum Discussion
Deployment Rules for Semantic Models - Change connection from DEV to TEST
- 1 year ago
LopesN ,
Thanks a lot for the update — and for sharing the PySpark workaround using semantic-link-labs, that’s super valuable for others who might hit the same wall.
From what you’ve described, it really looks like the Compare feature is holding onto some internal metadata reference tied to the original Lakehouse, and even after deletion + redeployment, it doesn’t fully reset.
Here’s a quick recap of what you tried (and a small tweak others might try too):
✅ What you did:
- Deleted the Lakehouse and all related Semantic Models
- Re-deployed from DEV
- Used this code to redirect the model to TEST:
%pip install semantic-link-labs from sempy.labs.directlake import update_direct_lake_model_lakehouse_connection dataset_name = "Lakehouse_Test_NLSM" # Name of the deployed dataset workspace_name = None # Optional: specify if needed lakehouse_name = None # Optional: specify if needed lakehouse_workspace_name = None # Optional: specify if needed update_direct_lake_model_lakehouse_connection( dataset = dataset_name, workspace = workspace_name, lakehouse = lakehouse_name, lakehouse_workspace = lakehouse_workspace_name )This is a solid approach — but unfortunately, as you said, Compare still fails, even with a clean redeploy.
🔍 What else to try:
- Try creating a completely new Lakehouse (with a different name) and deploy a fresh Semantic Model on top of it. If Compare works there, it confirms the issue is tied to internal lineage/cache on the original Lakehouse.
- If you’re comfortable, try using the Fabric REST APIs to inspect or reset lineage metadata (though this is more advanced and not always exposed).
- Definitely raise this with Microsoft Fabric support — this feels like a backend issue that needs cleanup on their side.
Let me know if you want help testing with a minimal setup — happy to assist.
If my response resolved your query, kindly mark it as the Accepted Solution to assist others. Additionally, I would be grateful for a 'Kudos' if you found my response helpful.
*This response was supported by AI for translation and text editing purposes.
Hello LopesN,
Sorry for the inconvenience caused. Please consider raising a Microsoft support ticket for further investigation. You can explain all the troubleshooting steps you have taken to help them better understand the issue.
You can create a Microsoft support ticket with the help of the link below:
https://learn.microsoft.com/en-us/power-bi/support/create-support-ticket
If this helps, please accept it as a solution and drop a "Kudos" so other members can find it more easily.
Thank you.
Hello LopesN,
We are following up once again regarding your query. Could you please confirm if the issue has been resolved through the support ticket with Microsoft?
If the issue has been resolved, we kindly request you to share the resolution or key insights here to help others in the community. If we don’t hear back, we’ll go ahead and close this thread.
Should you need further assistance in the future, we encourage you to reach out via the Microsoft Fabric Community Forum and create a new thread. We’ll be happy to help.
Thank you for your understanding.
- LopesN1 year agoFrequent Visitor
Hello v-ssriganesh ,
After further testing, the problem is still happening.
I will follow up and create a ticket or a new thread on the Community Forum to see if I get some feedback.
Thank you.