...
“limit” specifies the number of data items to be shown per page in the result object. The maximum value is 999. Always specify a limit. If you do not specify a limit and there are more than 999 results, it will return an invalid number of results.
“page” is the page number to be shown in the results object. The first page starts at 1.
“sortBy” is used to sort the fetched data based on the criteria.
For example, {"sortBy":{"modifiedAt":-1}} will sort the data items shown in the result array based on the modified date displaying the latest modified data item first.
...
Because we are doing a loop to get all the pages of data, it is a good idea while testing to add a delay to throttle the number of queries query requests, in case you make a mistake and created an infinite loop. Then either change the delay to 1 ms , or remove the delay completely.
...
The Dynamic Data Manager mode node is set to Read.
AND condition of version, CreatedAt, Page
limit says for this page do not bring back more than 999 items. Which is the max limit.
...
Ignore the red X in this example, the validation is confused by the mustache tag, msg.pagePnter is a number. sortBy, in this case, we used createdAt.
The createdAt & , modifiedAt & , and _id are always returned in the collection.
...
The init function node sets up the pagePntr to start at 1. A common mistake is to start at 0.
Also setting up the array to store the results, in this case, msg.userDataArray = [ ]
...
| Code Block |
|---|
msg.pagePntr = 1; // init page pointer to 1
msg.userDataArray = []; // init aray
var moment = global.get('moment');
const now = moment(); // use moment to creat time 20 days earlier than today
const DaysAgo = now.subtract(20, "days").startOf("day").utc().toISOString();
node.warn(DaysAgo); // "2020-11-16T00:00:00.000Z"
msg.startDate = DaysAgo;
return msg; |
The loop function node concatenates the results of each page , until it collects all the data.
...