March 31 - April 2, 2025, in Las Vegas, Nevada. Use code MSCUST for a $150 discount! Early bird discount ends December 31.
Register NowBe one of the first to start using Fabric Databases. View on-demand sessions with database experts and the Microsoft product team to learn just how easy it is to get started. Watch now
Hello,
I plan to configure incremental refresh.
Suppose we have data from 2015-2020. In addition, we have 2 columns - extraction date (update date) and sale date. We want to refresh data that has been extracted (updated) in the last 30 days.
What happens if we make some changes to the data from 2018 (The update date will change to the current date)?
Will PowerBI delete old lines and replace them with new lines? Will the rows be duplicated and will I need to detect changes and manually remove the duplicate rows?
Thank you in advance,
Jagoda
Solved! Go to Solution.
Hi @Anonymous ,
Based on my understand, if we set store rows for where "extraction date" is in the last 5 years and refresh rows where "extraction date" is in the last 30 days, then the refresh start at 2020-03-14 06:00:00 AM, it will refresh the rows where "extraction date" is between 2020-02-13 06:00:00 AM and 2020-03-14 06:00:00 AM, and all the rows where "extraction date" is between 2015-03-14 06:00:00 AM and between 2020-02-13 06:00:00 AM will keep as the same, and then the rows where "extraction date" is earlier than the 2020-02-13 06:00:00 AM will be dropped.
So In your scenario, if the data in 2018 changed to earlier than 2020-02-13 06:00:00 AM,those rows will not change and keep as old if the refresh range is only set as 30 days. If it change to 2020-03-12 08:00:00, Based on our test, it will keep the old row and add a new rows:
Please refer to following document about more information of Incremental Refresh:
Best regards,
Hi @Anonymous ,
Based on my understand, if we set store rows for where "extraction date" is in the last 5 years and refresh rows where "extraction date" is in the last 30 days, then the refresh start at 2020-03-14 06:00:00 AM, it will refresh the rows where "extraction date" is between 2020-02-13 06:00:00 AM and 2020-03-14 06:00:00 AM, and all the rows where "extraction date" is between 2015-03-14 06:00:00 AM and between 2020-02-13 06:00:00 AM will keep as the same, and then the rows where "extraction date" is earlier than the 2020-02-13 06:00:00 AM will be dropped.
So In your scenario, if the data in 2018 changed to earlier than 2020-02-13 06:00:00 AM,those rows will not change and keep as old if the refresh range is only set as 30 days. If it change to 2020-03-12 08:00:00, Based on our test, it will keep the old row and add a new rows:
Please refer to following document about more information of Incremental Refresh:
Best regards,
is there a way to prevent duplication of records, and just update the "old" record with the"new" one? without having to refresh on the entire period of 5 years?
Does anyone have a proposal how to solve this? We have exactly the same issue.
Since the underlying technology is SSAS, can this be done in SSAS or AS models too?
March 31 - April 2, 2025, in Las Vegas, Nevada. Use code MSCUST for a $150 discount!
Your insights matter. That’s why we created a quick survey to learn about your experience finding answers to technical questions.
Arun Ulag shares exciting details about the Microsoft Fabric Conference 2025, which will be held in Las Vegas, NV.
User | Count |
---|---|
40 | |
26 | |
17 | |
11 | |
10 |
User | Count |
---|---|
57 | |
52 | |
23 | |
13 | |
11 |