Don't miss your chance to take the Fabric Data Engineer (DP-700) exam on us!
Learn moreNext up in the FabCon + SQLCon recap series: The roadmap for Microsoft SQL and Maximizing Developer experiences in Fabric. All sessions are available on-demand after the live show. Register now
Hi,
I would appreciate if you can guide me on the best way to handle this:
I am creating a Balance report in PBI, where I need the data from 2 years back to today (I am using JD Edwards).
Of course I already made a query that extracts the data, but the Refresh is a bit slow.
So I wanted to do the following:
a. To have the data from 2020 to last month, in a table that will be refreshed monthly, the day of accounting close. (It would be the Historical data)
b. On the other hand, to have in another table that makes the daily refresh with the transactions of the day to have the information of the current month.
This way I could make a UNION or MERGE to join both tables and in this way, the report would be faster.
I would appreciate if you can guide me on how to handle it.
Note: I don't if it is possible to schedule a refresh in different times for two tables in the same report..
Greetings.
Solved! Go to Solution.
Hi, @gomezc73
Incremental Refresh is the process of loading only part of the data that might change, and adding it to the previous dataset which is not changing anymore.
Incremental refresh extends scheduled refresh operations by providing automated partition creation and management for dataset tables that frequently load new and updated data.
With incremental refresh, the service dynamically partitions and separates data that needs to be refreshed frequently from data that can be refreshed less frequently.
Refer:
Incremental refresh and real-time data for datasets
Configure incremental refresh and real-time data
More:
https://www.sqlshack.com/an-overview-of-power-bi-incremental-refresh/
https://biinsight.com/implementing-incremental-refresh-in-power-bi-part-1/
https://radacad.com/all-you-need-to-know-about-the-incremental-refresh-in-power-bi-load-changes-only
Best Regards,
Community Support Team _ Zeon Zheng
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
Hi, @gomezc73
Incremental Refresh is the process of loading only part of the data that might change, and adding it to the previous dataset which is not changing anymore.
Incremental refresh extends scheduled refresh operations by providing automated partition creation and management for dataset tables that frequently load new and updated data.
With incremental refresh, the service dynamically partitions and separates data that needs to be refreshed frequently from data that can be refreshed less frequently.
Refer:
Incremental refresh and real-time data for datasets
Configure incremental refresh and real-time data
More:
https://www.sqlshack.com/an-overview-of-power-bi-incremental-refresh/
https://biinsight.com/implementing-incremental-refresh-in-power-bi-part-1/
https://radacad.com/all-you-need-to-know-about-the-incremental-refresh-in-power-bi-load-changes-only
Best Regards,
Community Support Team _ Zeon Zheng
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
Thank you, this information is very useful
@v-angzheng-msft be careful not to mix up incremental refresh with differential refresh. Incremental refresh does NOT address data changes. It assumes immutability of data written to older partitions. It should have been called "Selective Partition Flush&Fill" but that probably wasn't a cool enough name.
Hi, @lbendlin
Thanks for your reply, the above statement comes entirely from the article above.
Best Regards,
Community Support Team _ Zeon Zheng
You don't really need to do that. Read about Incremental Refresh.
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 |
|---|---|
| 48 | |
| 44 | |
| 42 | |
| 18 | |
| 18 |
| User | Count |
|---|---|
| 72 | |
| 66 | |
| 33 | |
| 32 | |
| 31 |