Thanks Ulrik,
Btw huge fan and follow your blog extensively.
So the reason I'm looking at incremental refresh is say for example I've got two tables/entities that I want to bring into Power BI.
I want to bring in opportunities from say the 1st of January 2020 onwards indefinitely. I also need all the emails related to the opportunity because I want to aggregate the number of sent emails per opportunity but also to drill down to the individual emails.
The problem comes is if I don't set the fetch xml query to a specific date range or use one of the relative date filters like created on equals this year. It'll continue to pull more and more data from the CRM via the API using Power Query builder. Especially when it comes to email activities, the CRM generates alot of it. I'm just thinking of the overall refresh time as more and more data needs to be imported into Power BI.
This was why I was looking at incremental refresh. Basically I want to only import data that's changed in CRM like for example of the last modified date on the opportunity has changed, bring it in and update. If a new email was created and sent, bring it in and update/create the record in Power BI.
This off course assumes the query folds back to CRM so that it only brings in the records that were last changed and not everything and then apply the filter.
Also is there another way of doing this more efficiently in Power BI?
Kind regards,
Mike
