Backwards Deployment

C0L0mbo,

Backward deployment (PROD -> DEV) can lead to metadata inconsistencies, especially if Workspace IDs or item references are manually updated.

A few questions to help narrow this down:

• Are the affected tables coming from Dataflows Gen2, Lakehouse, or another source?
• After the deployment, did you refresh the dataflows first and then the semantic model?
• Were there any warnings or skipped items shown in the deployment pipeline?

Blank tables and missing relationships can occur if the semantic model is still referencing old object IDs or if upstream artifacts weren't fully synchronized after deployment. I'd also recommend comparing the DEV semantic model with PROD to verify that all tables, relationships, and source bindings were deployed correctly.

If possible, could you share the deployment pipeline configuration and any error messages you are seeing? That would help identify the root cause.

Best regards,
Omkar Shinde
Microsoft Fabric Enthusiast | Power BI Consultant

💡 If you found this response helpful, please consider giving it a Kudos.
✅ If this resolves your question, please mark it as the Accepted Solution to help others in the community.