Forum Discussion
Increment Refresh Clarifications
Yeah, sorry GK600 - I understand. That is how it goes with self service projects. If you can get the system to export in to Excel format or CSV format, you can get things working, but there will be no incremental refresh on those either, the point of your original post.
If you have any problems going forward, start a new thread and we will jump in and help. In the mean time, please mark one or more of these posts as the solution so this thread can be marked as solved - even though not solved in the way you were hoping. 😉
Incremental Refresh requires query folding. Web APIs do not count. You would need an ODATA feed, or a true database like CDS, SQL Server, Azure SQL, Oracle, etc. And as you've discovered, if View Native Query is greyed out, you cannot do it. (There are very rare cases where that is not correct - greyed out and it still folds, but those are edge cases with SQL Server/Oracle, etc. and you can use your database profiling tool to see that even though the PQ UI thinks folding has broken, it is really continuing. This is only for a few command. Retrieving top rows I believe will cause this glitch to manifest)
It requires query folding because the service partitions your data and will generate a different SQL statement for each one - so the current refresh data goes in one partition with one set of data, and the old stuff goes in another partition, then the service will move data between those as they age out of the "current" dataset.