module function · N/workbook

createLimitingFilter()

workbook.createLimitingFilter(options)

Creates a limiting filter.

Implementation
Not started
Design
Open for proposals suggest how it should read
Proposals
A
Signature
workbook.createLimitingFilter(options)
Returns
workbook.LimitingFilter
Governance
None
Script types
Server scripts
Version
SuiteScript 2.x, documented for 2.1; since NetSuite 2020.2
call shapefrom Oracle's parameter table
1workbook.createLimitingFilter({2    limit:   /* number, required */,3    row:     /* boolean, required */,4    sortBys: /* Array< workbook.SortByDataDimensionItem | workbook.SortByMeasure >, required */5});
Oracle reference for this method
ParameterTypeRequiredDescription
options.limitnumberrequiredThe limit for the limiting filter.
options.rowbooleanrequiredIndicator for a row axis filter. If set to false, the filter is a on a column axis.
options.sortBysArray< workbook.SortByDataDimensionItem | workbook.SortByMeasure >requiredThe sort order for the limiting filter.
B

No Mynt syntax yet.

Nothing in the language compiles to workbook.createLimitingFilter(options) today. How should it read?

C

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

All discussions

Loading proposals from GitHub…

D

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/workbook · workbook.createLimitingFilter(options)

Suggest syntax for createLimitingFilter