Forum Discussion

TK12345's avatar
TK12345
Resolver II
1 month ago

Materialized Lake View Refresh activity Pipeline bug

Hi all, 

When using the preview feature refresh mlv activity in the pipeline, is do have some major bugs. After saving, it goes back to default, the pipeline does not want to refresh after, and I cannot parametrize it. 

Is there any workarround, and is this a known bug?

Cause this is not workable. 

8 Replies

  • v-achippa's avatar
    v-achippa
    Community Support

    Hi TK12345,

     

    Thank you for reaching out to Microsoft Fabric Community.

     

    Since the Refresh Materialized Lake View activity is currently in preview,looks like the issue here is likely related to the preview implementation. This is not expected behaviour and there is no documented workaround for the save/reset or parameterization issues.

    I recommend raising a Microsoft Fabric support ticket so the product team can investigate the issue from the backend.

    Create a Fabric and Power BI Support Ticket - Power BI | Microsoft Learn

     

    Thanks and regards,

    Anjan Kumar Chippa

    • v-achippa's avatar
      v-achippa
      Community Support

      Hi TK12345,

       

      As we haven’t heard back from you, we wanted to kindly follow up to check if the response I have provided for the issue worked? or have you raised a support ticket?

       

      Thanks and regards,

      Anjan Kumar Chippa

      • v-achippa's avatar
        v-achippa
        Community Support

        Hi @TK12345,

         

        We wanted to kindly follow up to check if the response I have provided for the issue worked? or have you raised a support ticket?

         

        Thanks and regards,

        Anjan Kumar Chippa

    • philip_gray's avatar
      philip_gray
      Regular Visitor

      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?

      • TK12345's avatar
        TK12345
        Resolver II

        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.