It's possible to page with GetListItemChangesSinceTokenAsync. For instance, if the result returns a ListItemCollectionPositionNext value, you know there are more results.
When make the call to retrive those results however, you must set changeToken to null. When I inserted the changeToken in a query for more paged results, I got zero results, which may seem counterintuitive, but actually makes sense because adding a changeToken that implicitely pointed to the next result set would be redundant as ListItemCollectionPositionNext already indicates this.
Replace nested-if's with proper exception-handling
-
" Why handle exceptions separately:
■ Handling exceptions separately enables you to define the main logic of
your
code together.
■ Without the use of sepa...
2 years ago
No comments:
Post a Comment