Deployment pipeline - data updates to target

[CarlBlunck]

Hi all,

We are trying to understand what happens to the datasets in the target workspace when a deployment pipeline is run.

From what we understand, if we are moving across a:

1. Data pipeline
2. Notebooks
3. Lakehouse
4. Semantic model
5. Reports

All in the same data pipeline, the data in target for the:

1. Lakehouse
2. Semantic model

Does not get copied across and the data in the lakehouse/semantic model will remain the same until a refresh is undertaken in that workspace.

Is this correct?

If so, my question is, how does a report continue to operate when it has been updated through the pipeline, but the lakehouse/semantic model it is reading off has not been updated?

Thanks

Carl

[lbendlin]

It depends on the severity of the meta data changes.  Some changes have no impact at all, while others (like the deletion of a column that is used in the report visuals) will break these visuals.

[v-mdharahman · Accepted solution]

Hi @CarlBlunck,

Thanks for reaching out to the Microsoft fabric community forum.

You are right in your understanding of pipeline deployment in Microsoft Fabric. In Lakehouse & Semantic Model only the metadata and structure are copied to the target workspace. The actual data is not moved and in reports & dsshboards they get updated with the latest changes like visual modifications, but they still reference the existing data from the semantic model, which has not been refreshed. 

Coming to the second point even though the report is updated in the target workspace, it still connects to the same semantic model, which contains the old data. If the semantic model structure remains unchanged, the report will function normally, but it won’t show updated data until the semantic model and lakehouse are refreshed. 

If you want your report to reflect the latest data after deployment, you can manually refresh the Lakehouse and Semantic Model in the target workspace. Or automate refresh via Data Pipeline or use Deployment Pipeline refresh option which automatically refresh datasets after each deployment.

I would also take a moment to thank @lbendlin, for actively participating in the community forum and for the solutions you’ve been sharing in the community forum. Your contributions make a real difference.

If I misunderstand your needs or you still have problems on it, please feel free to let us know.  

Best Regards,
Hammad.
Community Support Team

If this post helps then please mark it as a solution, so that other members find it more quickly.

Thank you.

[v-mdharahman]

Hi @CarlBlunck,

As we haven’t heard back from you, so just following up to our previous message. I'd like to confirm if you've successfully resolved this issue or if you need further help.

If yes, you are welcome to share your workaround and mark it as a solution so that other users can benefit as well. If you find a reply particularly helpful to you, you can also mark it as a solution.

If you still have any questions or need more support, please feel free to let us know. We are more than happy to continue to help you.
Thank you for your patience and look forward to hearing from you.

[v-mdharahman]

Hi @CarlBlunck,

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 so that other community members can find it easily.

Thank you.

[v-mdharahman]

Hi @CarlBlunck,

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.