Using fetchMoreData/dataReduction for pagination

Hi ChadK,

fetchMoreData only moves in one direction (incrementally) when called, so with the current functionality, you will need to handle the changes to the data view and tracking pagination via your visual logic. Previous pages will very much be present in the data view. You would probably also need to consider what might happen when the dataset is fully refreshed in the event of 'volatile' changes on the page (e.g., filtering or cross-filtering from other visuals) and whether the visual state can be reliably managed in these cases for pagination to track correctly (it might be easier to reset this back to the first page whenever this happens rather than diffing memoized data views vs. new ones and recursively calling fetchMoreData to get back to approximately the same place as before).

Any changes to this API would need to be a feature request to MS: [email protected]

Regards,

Daniel