Forum Discussion
Cross-lakehouse execution MLVs Trigger
Hi all,
I saw a very great update on the MLV's with the option for Cross-lakehouse execution. I've read a lot of documentation, tested the execute button and schedule options. But I would like to know, is there also a possibitity to trigger this? Cause for example I schedule it for 03:00 but my extraction is not ready yet. Is there a trigger I can use in a notebook or pipeline to start the Cross-lakehouse execution, so the mlv's are refreshing in the right sequence? Maybe it is not yet released, but would be great.
https://learn.microsoft.com/en-us/fabric/data-engineering/materialized-lake-views/view-lineage
Hi TK12345 ,The current approach using Fabric REST APIs does not support cross-workspace execution, and it also does not take dependencies or lineage between MLVs into account when triggering refreshes.
So in your case, where you need cross-lakehouse execution with proper sequencing based on upstream readiness, this limitation means there’s no out-of-the-box solution yet, you would have to manage orchestration manually. Given this gap, it would be a good idea to raise this as a feature request in the Microsoft Fabric Ideas portal, specifically highlighting the need for event-based triggers and dependency-aware execution across workspaces.
Thanks,
prashanth Are
4 Replies
Hello TK12345
You can refresh MLVs programatically using Fabric REST API endpoints, documentation link below. There is no native event based trigger yet.Manage Fabric materialized lake views with public APIs - Microsoft Fabric | Microsoft Learn
Hi,
Thanks for your reply, but this one is not across workspaces and does not look to the dependencies right?Hi TK12345 ,The current approach using Fabric REST APIs does not support cross-workspace execution, and it also does not take dependencies or lineage between MLVs into account when triggering refreshes.
So in your case, where you need cross-lakehouse execution with proper sequencing based on upstream readiness, this limitation means there’s no out-of-the-box solution yet, you would have to manage orchestration manually. Given this gap, it would be a good idea to raise this as a feature request in the Microsoft Fabric Ideas portal, specifically highlighting the need for event-based triggers and dependency-aware execution across workspaces.
Thanks,
prashanth Are
We are following up once again regarding your query. Could you please confirm if you have raised ideas with Microsoft?
If not please raise idea and upvote it. 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.
