Forum Discussion
incremental refresh with Web.Contents not working
Exactly, it's just a warning, not an error message. If you know that your data source honors the RangeStart/RangeEnd parameters (in the appropriate format conversion ) then incremental refresh will work. The only sure way to validate incremental refresh is to look at the partition statistics in the XMLA endpoint. If you see only one partition then incremental refresh likely doesn't work. If you see multiple partitions then it works. I have a blog entry on that subject if you are interested.
Exactly, it's just a warning, not an error message. If you know that your data source honors the RangeStart/RangeEnd parameters (in the appropriate format conversion ) then incremental refresh will work. The only sure way to validate incremental refresh is to look at the partition statistics in the XMLA endpoint. If you see only one partition then incremental refresh likely doesn't work. If you see multiple partitions then it works. I have a blog entry on that subject if you are interested.
Finally got this to work, thanks! A few things to note, though:
- Incremental refresh seems to query data one day at a time, perhaps only for the initial data set retrieval; in my case this sometimes resulted in no data being returned, which the M script choked on
- JSON objects seem to be translated to M records and JSON arrays to M lists by the Json.Document function, but that is not documented (you can infer it from the inverse mapping documented for Json.Value, though)
- After publishing a new version of this project to the PBI service I kept getting a “gateway needed” error the first time it was refreshed in the service, but not after that (and everything worked as expected without gateway), nor with automatic refresh after that