Question

You maintain a large enterprise semantic model in a Fabric Premium workspace. A colleague made structural changes (new calculated columns and measures) directly in a development workspace model using an external tool. You now need to promote ONLY those metadata differences to the production model without overwriting production-only partitions or triggering a full data reload. Which approach best accomplishes this?

Accepted Answer

Use the ALM Toolkit connected to both models via the XMLA endpoint to compare schemas and selectively deploy only the changed metadata objects.

Answer

Download the development model as a .pbix from the service and re-publish it over the production model.

Answer

Create a deployment pipeline and click Deploy, which always copies only metadata and never affects data.

Answer

Export the development model as a .pbit template and import it into the production workspace.