Query object method · N/query
runPaged()
Query.runPaged(options)
Executes the query and returns a set of paged results.
- Implementation
- Not started used inside other constructs
- Design
- Open for proposals suggest how it should read
A
suitescript api
1objQuery.runPaged({2 pageSize: /* string, optional */,3 customScriptId: /* string, optional */4});| Parameter | Type | Required | Description |
|---|---|---|---|
| options.pageSize | string | optional | The size of each page in the query results. The default page size is 50 results per page. |
| options.customScriptId | string | optional | A unique identifier used for potential performance issues in a query. If your query produces performance issues, the custom script ID identifies where the update will need to occur. This ID can also be used as a precaution to speed up performance fixes, if necessary. Note: The Script ID must be unique or the performance enhancements will affect each query with the same customScriptID. |
B
mynt syntax
No syntax of its own.
The compiler already calls Query.runPaged(options) inside query T, so programs use it without naming it. Writing it directly has no syntax yet.
C
community proposals
Competing syntax for runPaged, from GitHub Discussions. Select two or more to compare them side by side.
Loading proposals from GitHub…
D
suggest an alternative
Write the Mynt you wish you could write.
A good proposal shows the syntax, the SuiteScript it should become, and argues for it: why it is clearer, how it fits the rest of the language, what it makes harder.
- Clarity. Does it say what happens, without ceremony?
- Consistency. Does it read like
load,saveandRef[field]? - Expressiveness. Does it cover the cases people actually write?
- Honesty. Does it hide a NetSuite cost, such as governance, that a reader should see?