This time we’re going bigger than ever. Fabric, Power BI, SQL, AI and more. We're covering it all. You won't want to miss it.
Learn moreLevel up your Power BI skills this month - build one visual each week and tell better stories with data! Get started
Hi everyone, I am currently trying to do an incremental historical load of an entity in a dataflow using the REST API.
The query in the dataflow uses a NativeQuery. I would like to avoid loading the full history at once, so I am trying the following method (currently testing out with dummy data):
- write out the query as a native query and specify "WHERE 1 = 0" in the sql so that no rows are loaded.
-refresh the dataflow with an incremental refresh policy defined, so that partitions are created with no rows
-reopen the dataflow and change the native query to "WHERE 1 = 1"
-save the dataflow, but don't refresh it so that no data is loaded.
-use the REST API to refresh an individual partition and repeat until I have loaded all the partitions necessary
In the microsoft interface, I am trying to call the REST API like so:
However, when I check the refresh history, all of the partitions get populated instead of just the one I specify (Nov 4th in the example above). Just wondering if the issue is with the parameters I am sending to the REST API or if there is a problem with my method?
Just noticed that the Enhanced refresh with the Power BI REST API - Power BI | Microsoft Learn seems to be referring to Datasets only. It seems like the only configurable parameter for a dataflow refresh is whether an email notification is delivered on failure or not.
Check out the April 2026 Power BI update to learn about new features.
Sign up to receive a private message when registration opens and key events begin.
If you have recently started exploring Fabric, we'd love to hear how it's going. Your feedback can help with product improvements.
| User | Count |
|---|---|
| 11 | |
| 9 | |
| 9 | |
| 8 | |
| 8 |
| User | Count |
|---|---|
| 48 | |
| 27 | |
| 25 | |
| 24 | |
| 22 |