https://docs.microsoft.com/en-us/power-bi/admin/service-premium-incremental-refresh
https://docs.microsoft.com/en-us/power-bi/admin/service-premium-incremental-refresh#configure-incremental-refresh
Making incremental refresh possible, out-of-the-box, will increase the performance of the data refresh, since less data will need to be refreshed, in for example ledger entry tables.
Comments
Definetely a must have !
Category: Reports and Business Intelligence
Definitely a must have. Full sync is a drag.. And manual workarounds not optimal
Category: Reports and Business Intelligence
This should be a no brainer to add, It will make updates to Power BI faster and at the same time use less ressources on server both in SaaS and onprem. Win/Win!
Category: Reports and Business Intelligence
It's a struggle to get data from Business central to Power BI.
I can't help but feel that there are a lot of people "reinventing the wheel" to get this working.
Using the API's is terribly slow and, I imagine, a big consumer of resources in the cloud.
This suggestions is great, but should be part of a larger project to have a high performance data store available to PowerBI. Just put it in a data lake or something like that.
Category: Reports and Business Intelligence
At this moment we have problems with customers who moved from on prem to cloud. The "old" Power BI reports get many run time errors due to full sync of historical data, which is not needed. Please implement incremental refresh. So we also can use "last updated" option for tables with no historical data such as "Customer".
Category: Reports and Business Intelligence
As more people become aware of incremental refresh they will use it more. I know people use it with SQL but It will be great to let users with BC on prem. benefit with the feature too.
Example: We have a customer with a large (5 years of data - 1.4 gb) G_LEntries table . For an A/R report I made I have to use Odata filtering for the accounts I just need (/G_LEntries?$filter=G_L_Account_No ge '40000' and G_L_Account_No le '49999'") still, I get 184 mb of data for all 5 years. For this report I'll only need to refresh it for any changes of the "Posting Date" in the last 7 days. I believe incremental refresh should let me do that and in that case it should not be more than few mbs.
At this moment I'm forced to filter and split (Duplicating) the G_LEntries table. Then I filter the original source by the posting date starting 01/01/2020 and let auto refresh update it every day. The other table is set to not update and it contains all the records from 01/01/2016 to 12/31/2019.
The biggest downside of that is maintenance. You are forced to update the date ranges for both tables as the original table grows in order to avoid delays or time outs. The other downside is consistency. If the customer did not close previous years you are forced to extend the amount time you will sync every day since old invoices might get paid.
Category: Reports and Business Intelligence
If Microsoft develops this, then they will gain in performance on their servers (which is a cost saver for them) and also the customer will profit is less loading times.
Category: Reports and Business Intelligence
We really need this to happen
Category: Reports and Business Intelligence
Business Central Team (administrator)
Thank you for this suggestion! Currently this is not on our roadmap. We are tracking this idea and if it gathers more votes and comments we will consider it in the future. Best regards, Business Central Team