Starting December 3, join live sessions with database experts and the Microsoft product team to learn just how easy it is to get started
Learn moreGet certified in Microsoft Fabric—for free! For a limited time, get a free DP-600 exam voucher to use by the end of 2024. Register now
Haven't found any documentation on how data refresh works with respect to a dataflow and then a dataset sourced from that dataflow.
So looking for feedback, based on what I've discovered:
I've come to this conclusion after seeing the behaviour of having one or the other set for scheduled refresh.
I'm also seeing inconsistency in the workspace contents view where it shows last and next refresh times.
For this dataflow, I've toggled off the scheduled refresh but it still shows a Next Refresh time (I would expect not to see any time stamp):
For these datasets, they have both had a refresh more recently than indicated here
Here's the first one:
And the second:
A bug?
Solved! Go to Solution.
>So I assume the dataflow is much like a data storage component on its own that manages the updating from the data source, wherever that may be
That's correct, technically PBI's Dataflow uses Azure Data Lake Gen2 for storage.
One use case I plan to use this dual refresh structure for, is to handle sources (e.g. static files) that don't need to be refreshed in Dataflows where they'll be imported but not under scheduled refresh. I've found PBI's scheduled refreshes to fail easily, so cutting down the service's scheduled refreshes to sources that actually need to be refreshed should lower incidents (e.g. web API timeouts, credential issues etc.).
Hi,
After internal checking, it seems that the next refresh time update (without browser refresh) was fixed and is should be available in the following updates.
I will keep monitor it.
Thanks,
Assaf
The above link not going anywhere.
I think I've found the session here:
Hi,
NotifyOption in Power Automate custom connector for either dataflow or dataset refresh is not working for me.
Anyone recived mail on completion?
Hi!
Regarding the inconsistency in the next refresh time of the dataflow, after a browser refresh, do you still see the next refresh time?
Thanks,
Assaf
@Assaf wrote:
Regarding the inconsistency in the next refresh time of the dataflow, after a browser refresh, do you still see the next refresh time?
I do see the refresh time after a browser refresh. Also with the page remaining on screen, the refresh was scheduled to run and the date/time stamps updated without me having to refresh.
The issue I was experiencing included navigating away from that pgae, then returning to the page (so not refreshing the browser), so I'd have thought that would result in the updated time stamps too...I'll keep an eye on it.
Hi,
After internal checking, it seems that the next refresh time update (without browser refresh) was fixed and is should be available in the following updates.
I will keep monitor it.
Thanks,
Assaf
I've noticed the date & time stamps are now updating, even without any refresh or navigating away.
Good to hear. Thanks!
>So I assume the dataflow is much like a data storage component on its own that manages the updating from the data source, wherever that may be
That's correct, technically PBI's Dataflow uses Azure Data Lake Gen2 for storage.
One use case I plan to use this dual refresh structure for, is to handle sources (e.g. static files) that don't need to be refreshed in Dataflows where they'll be imported but not under scheduled refresh. I've found PBI's scheduled refreshes to fail easily, so cutting down the service's scheduled refreshes to sources that actually need to be refreshed should lower incidents (e.g. web API timeouts, credential issues etc.).
Starting December 3, join live sessions with database experts and the Fabric product team to learn just how easy it is to get started.
March 31 - April 2, 2025, in Las Vegas, Nevada. Use code MSCUST for a $150 discount! Early Bird pricing ends December 9th.
User | Count |
---|---|
34 | |
30 | |
18 | |
12 | |
8 |
User | Count |
---|---|
50 | |
35 | |
30 | |
14 | |
12 |