Register now to learn Fabric in free live sessions led by the best Microsoft experts. From Apr 16 to May 9, in English and Spanish.
Hi All,
Been doing quite a bit of testing using Incremental Refresh with Detect Data turned on. It was setup as a very, very simple controlled test using a table that just had a Main Date, Modified Date, and a Value.
I would manually update the test table in a variety of ways, then refresh my PBI report and view the results.
What I'm finding is that sometimes everything works exactly as expected: new rows get picked up, changed rows get picked up, rows that fall outside the date ranges get ignored, etc. etc.
But then for some reason, I always find that the Detect Data seems to stop working. Then for awhile I do not see new rows being added or valid updates to the data being reflected. I'll continue to refresh and it simply doesn't work.
But then I'll make another change to the table and suddenly everything seems to "wake up" and then it will start working again. But this will only last awhile until it then seems to lose track and stop updating again.
And again, this is a very simple and controlled data table which I am manually updating, so I know exactly the rows that are being sent.
I was wondering if anyone has experienced something similar, or if maybe someone knows about some nuances with how Detect Data works that may explain this kind of erratic behavior...
Thanks!
Here's a good example of what I'm referring to.
Note how I added a new row at Index 13 and you can see it in the control table on the left. When I did the refresh, the Incremental Refresh table on the right did pick it up.
A few minutes later, I added row Index 14 with the same dates. You can see it in the control table on the left. But then note how the Incremental Refresh table on the right does not pick it up.
Covering the world! 9:00-10:30 AM Sydney, 4:00-5:30 PM CET (Paris/Berlin), 7:00-8:30 PM Mexico City
Check out the April 2024 Power BI update to learn about new features.