We've captured the moments from FabCon & SQLCon that everyone is talking about, and we are bringing them to the community, live and on-demand. Starts on April 14th. Register now
Hi!
I have two queries, one which has incremental refresh (query A). And one that's refreshing normally (query B).
I then append these queries into a new one (query C).
So when I publish the report to Power BI Service and refresh the dataset the incremental refresh works for query A. Query B is also refreshing as it should. Query C however does not include all data from query A, only the initial data loaded into Power BI Desktop (depending on what I set the parameters RangeStart and RangeEnd to) before I published the report.
So, is it possible to have incremental refresh on one query, and append it with another query that does a regular refresh?
Solved! Go to Solution.
Hi @lbendlin,
Thanks, but I know that the RangeStart and RangeEnd parameters are just placeholders.
I think I've solved my issue! I had to setup incremental refresh on the appended table as well. So for the rows coming from the Query B (which I want to fully update everytime the report refreshes) I had to add a fake DateTime column (with the same name used in Query A for filtering with RangeStart and RangeEnd) and set it's value to todays date. When I then append them into Query C I filter that appended DateTime-column again there on RangeStart and RangeEnd.
If your result is impacted by the RangeStart and RangeEnd values then your incremental refresh does not actually work.
Use a XMLA client to verify that your partitions are created and updated according to the settings on the Power BI side (x years to keep, x months to update etc).
RangeStart and RangeEnd are just placeholders, and you can use them to limit the amount of data you ingest for development. The values in these fields are not relevant for the actual incremental refresh.
Hi @lbendlin,
Thanks, but I know that the RangeStart and RangeEnd parameters are just placeholders.
I think I've solved my issue! I had to setup incremental refresh on the appended table as well. So for the rows coming from the Query B (which I want to fully update everytime the report refreshes) I had to add a fake DateTime column (with the same name used in Query A for filtering with RangeStart and RangeEnd) and set it's value to todays date. When I then append them into Query C I filter that appended DateTime-column again there on RangeStart and RangeEnd.
It may depend on when in the ETL process you introduce the range filter. Normally you would want to do that at the very beginning of the query for Table A, and not (for example) at the end of Query C.
Yes, I get that. So now I do it at the beginning of Query A and then again in the appended Query C at the end. But I don't filter Query B with the range filters.
Seems to give me the result I want. Have to wait until tomorrow (CET) though to see if any new posts could be loaded.
Just wanted to let anyone who might be reading this know that the solution (described in the post marked as solution) worked.
If you have recently started exploring Fabric, we'd love to hear how it's going. Your feedback can help with product improvements.
A new Power BI DataViz World Championship is coming this June! Don't miss out on submitting your entry.
Share feedback directly with Fabric product managers, participate in targeted research studies and influence the Fabric roadmap.
| User | Count |
|---|---|
| 57 | |
| 38 | |
| 32 | |
| 18 | |
| 16 |
| User | Count |
|---|---|
| 66 | |
| 66 | |
| 40 | |
| 34 | |
| 25 |