Forum Discussion
Materialized Lake View Refresh activity Pipeline bug
Hello. I'm experiencing the same problem with this activity in a Fabric Pipeline - it essentially forces the user to chose between either breaking CI/CD (by hard-coding the connection, workspace and lakehouse) or hard-coding the change in GIT and updating fabric from the repo (thereby losing editor support because validation fails).
Neither of those options are good. Nor do I especially want to invoke an API call to fabric from the pipeline to refresh the MLV.
Now that the OP has raised a ticket for this, is it under active investigation? Is there anywhere that progress can be tracked?
Hi Philip,
I can tell you that I've had a call with the support team to show the issues.
The issue with the Materialized Lake View (MLV) refresh activity pipeline has been identified and resolved.
The internal team has already fixed the behaviour with the materialized activity and the deployment is schedule for three weeks from now.
- PhamilyGuy5 days agoNew Member
It seems this has not been deployed yet, as the issue persists.