Managing Semantic Model Updates in Deployment Pipelines

[SLiu374]

I am currently building a deployment pipeline with Test and Prod workspaces and have a few questions regarding semantic model updates:

1. If schema changes (e.g., adding new columns or transformations) are made to the semantic model, requiring it to be downloaded, updated, and republished to the workspace, will the deployment pipeline still be able to deploy the updated semantic model to the Prod workspace? Additionally, will reports built off of this semantic model maintain their connection and function properly after the update?

2. If multiple team members need to work on updating the semantic models simultaneously, what steps or processes should be followed to ensure the model stays synchronized across the team?

I would appreciate any guidance or best practices for handling these scenarios effectively. Thank you!

[v-venuppu]

Hi @SLiu374 ,

Thank you for reaching out to Microsoft Fabric Community.

Thank you @lbendlin for the prompt response.

I wanted to check if you had the opportunity to review the information provided and resolve the issue..?Please let us know if you need any further assistance.We are happy to help.

Thank you.

[lbendlin · Accepted solution]

1. yes, and yes

2. Connect the Dev stage of your deployment pipeline to a version control system (github or Azure DevOps).  Then have a process in place to "publish"  versions to the Prod workspace as you would in a regular release management process.