Power BI is turning 10, and we’re marking the occasion with a special community challenge. Use your creativity to tell a story, uncover trends, or highlight something unexpected.
Get startedJoin us for an expert-led overview of the tools and concepts you'll need to become a Certified Power BI Data Analyst and pass exam PL-300. Register now.
We have been using 20 to 30 dataflows for approximately two years without issue (aside from slow response times). Recently, we have two dataflows that "successfully" refresh but do not actually store the data.
Since this is occuring in a DF with a SQL server as a source AND a DF with multiple DFs as sources, we do not think it is a source issue.
Since this issue occurs on a DF that will load partial data (all of 2023, all of 2022, all of 2023 and part of 2022 - but not all of 2022 and 2023), we do not think that this is related to a step or transormation interaction with the underlying data (because everything will load, but not a once).
We are completely dependent upon two to three layers of DFs for our reporting. If we cannot solve for this issue, we will be forced to migrate quickly onto another platform (which is horribly problematic).
We are unfamiliar with any settings that we can change to avoid this behavior and have not experienced it until recently.
Any thoughts or ideas are welcomed because we at a loss for additional fixes to explore.
Hello @GopherGopher, and thank you for starting a conversation in the Service Forum. Please consider marking this reply as a Solution, once you have opened a new Issue.
This is your chance to engage directly with the engineering team behind Fabric and Power BI. Share your experiences and shape the future.
Check out the June 2025 Power BI update to learn about new features.
User | Count |
---|---|
58 | |
36 | |
27 | |
25 | |
25 |
User | Count |
---|---|
62 | |
53 | |
30 | |
24 | |
23 |