Forum Discussion
Incremental Refresh - Summary View or Detail View?
Hi All,
I have two imported views in my Power BI dataset:
Detail View (one row per conversation)
Summary View (aggregated by date and path)
Both views have an UpdateDateTime column.
For Incremental Refresh, what is the recommended approach?
Apply Incremental Refresh on both views?
Apply it only on the Detail View?
Any best practices for this scenario?
Thanks in advance.
For this setup I would apply incremental refresh to the Detail View, since it is usually the larger table and rows there are more likely append-only on UpdateDateTime.
The Summary View is trickier, because if late-arriving detail records can change yesterday's aggregates, a plain incremental refresh will leave those partitions stale. Either skip incremental refresh on the Summary and do a full load (often fine if it is small), or keep it on and enable "Detect data changes" pointing at a reliable max-modified column.
Before you turn it on, confirm UpdateDateTime is folding all the way to the source (check Native Query in the Power Query step) and that it really represents when the row was created or changed, not just when the view ran.
If the Summary can be derived from the Detail, the cleaner pattern is to incrementally refresh only the Detail and let the model handle the aggregation.
If this helped, a thumbs up and accepting the solution would be appreciated.
Best regards,
Shai Karmani
5 Replies
the data from summary view is from detail view.
I will suggest : Apply Incremental Refresh only on the Detail View and build the Summary View on top of it inside the model, not as a separate imported table with its own refresh.
Apply incremental refresh to both. Each table refreshes independently, so the summary view won't inherit the policy from the detail view. Partition both on UpdateDateTime with matching RangeStart/RangeEnd.
For this setup I would apply incremental refresh to the Detail View, since it is usually the larger table and rows there are more likely append-only on UpdateDateTime.
The Summary View is trickier, because if late-arriving detail records can change yesterday's aggregates, a plain incremental refresh will leave those partitions stale. Either skip incremental refresh on the Summary and do a full load (often fine if it is small), or keep it on and enable "Detect data changes" pointing at a reliable max-modified column.
Before you turn it on, confirm UpdateDateTime is folding all the way to the source (check Native Query in the Power Query step) and that it really represents when the row was created or changed, not just when the view ran.
If the Summary can be derived from the Detail, the cleaner pattern is to incrementally refresh only the Detail and let the model handle the aggregation.
If this helped, a thumbs up and accepting the solution would be appreciated.
Best regards,
Shai KarmaniHi manoj_0911
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.
Thank you.Hi manoj_0911
May I check if this issue has been resolved? If not, Please feel free to contact us if you have any further questions.
Thank you
