module function · N/workbook
createLimitingFilter()
workbook.createLimitingFilter(options)
Creates a limiting filter.
- Implementation
- Not started
- Design
- Open for proposals suggest how it should read
A
suitescript api
1workbook.createLimitingFilter({2 limit: /* number, required */,3 row: /* boolean, required */,4 sortBys: /* Array< workbook.SortByDataDimensionItem | workbook.SortByMeasure >, required */5});
| Parameter | Type | Required | Description |
|---|---|---|---|
| options.limit | number | required | The limit for the limiting filter. |
| options.row | boolean | required | Indicator for a row axis filter. If set to false, the filter is a on a column axis. |
| options.sortBys | Array< workbook.SortByDataDimensionItem | workbook.SortByMeasure > | required | The sort order for the limiting filter. |
B
mynt syntax
No Mynt syntax yet.
Nothing in the language compiles to workbook.createLimitingFilter(options) today. How should it read?
C
community proposals
Competing syntax for createLimitingFilter, 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?