Forum Discussion

bdpr_95's avatar
bdpr_95
Helper IV
1 year ago
Solved

Best Practices for Managing Incremental Refresh

Hi, I'm currently working on a Power BI project where we have three separate workspaces: one for development, one for QA, and one for production. Each workspace is synced to a corresponding branch i...
  • v-pnaroju-msft's avatar
    1 year ago

    Thank you, rohit1991, for your response.

    Hi bdpr_95,

    We appreciate your inquiry sent through the Microsoft Fabric Community Forum.

    Based on my understanding, you can configure and validate incremental refresh within your QA environment. The refresh logic defined using RangeStart and RangeEnd is embedded in the dataset’s metadata and will be retained when deployed to the production environment via your DevOps pipeline.

    While it is considered best practice to use production like data in the QA environment to ensure realistic validation, it is not mandatory. Once deployed to Production, you may update the data source or parameters, and Power BI will automatically perform a full refresh using the new production data source. Thereafter, the incremental refresh policy will be applied from that point onwards.

    Additionally, please find below the relevant links for your reference:
    Incremental refresh for semantic models in Power BI - Power BI | Microsoft Learn
    Configure incremental refresh for Power BI semantic models - Power BI | Microsoft Learn

    We hope the information provided will assist in resolving your issue. Should you have any further queries, please feel free to contact the Microsoft Fabric community.

    Thank you.