Search object method · N/search
runPaged()
Search.runPaged(options)
Runs the current search and returns a search.PagedData Object.
- Implementation
- Not started used inside other constructs
- Design
- Open for proposals suggest how it should read
A
suitescript api
1objSearch.runPaged({2 pageSize: /* number, optional */3});| Parameter | Type | Required | Description |
|---|---|---|---|
| options.pageSize | number | optional | Maximum number of entries per page There is an upper limit, a lower limit, and a default setting: The maximum number allowed is 1000. The minimum number allowed is 5. By default, the page size is set to 50 entries per page. |
B
mynt syntax
No syntax of its own.
The compiler already calls Search.runPaged(options) inside search T and load Search, 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?