mynt

PagedData object method · N/query

fetch()

PagedData.fetch(options)

Retrieves a page in the set of pages included in the PagedData object.

Implementation
Not started used inside other constructs
Design
Open for proposals suggest how it should read
Proposals
A suitescript api
Signature
PagedData.fetch(options)
Module
N/query
Returns
query.Page
Governance
None
Script types
Client and server scripts
Version
SuiteScript 2.x, documented for 2.1; since NetSuite 2018.1
call shapefrom Oracle's parameter table
1objPagedData.fetch({2    index: /* number, required */3});
Oracle reference for this method
ParameterTypeRequiredDescription
options.indexnumberrequiredThe index of the page to retrieve. Page indexes start at 0.
B mynt syntax

No syntax of its own.

The compiler already calls PagedData.fetch(options) inside query T, so programs use it without naming it. Writing it directly has no syntax yet.

C community proposals

Competing syntax for fetch, from GitHub Discussions. Select two or more to compare them side by side.

All discussions

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, save and Ref[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?

N/query · PagedData.fetch(options)

Suggest syntax for fetch