SuiteQL object method · N/query
runPaged()
SuiteQL.runPaged(options)
Runs the SuiteQL query as a paged query and returns the paged query results.
- Implementation
- Not started
- Design
- Open for proposals suggest how it should read
A
suitescript api
1objSuiteQL.runPaged({2 pageSize: /* number, optional */,3 customScriptId: /* string, optional */4});| Parameter | Type | Required | Description |
|---|---|---|---|
| options.pageSize | number | optional | The size of each page in the query results. The default value is 50 results per page. The minimum page size is 5 results per page, and the maximum page size is 1000 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 Mynt syntax yet.
Nothing in the language compiles to SuiteQL.runPaged(options) today. How should it read?
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?