module function · N/workbook
createTableColumnFilter()
workbook.createTableColumnFilter(options)
Creates a table filter.
- Implementation
- Not started
- Design
- Open for proposals suggest how it should read
A
suitescript api
1workbook.createTableColumnFilter({2 operator: /* string, required */,3 values: /* Array<null | Object | number | string | boolean | Date>, optional */4});| Parameter | Type | Required | Description |
|---|---|---|---|
| options.operator | string | required | The operator for the filter. Values correspond to those in query.Operator . For instance, you can use the string value 'EMPTY', which corresponds to query.Operator.EMPTY. |
| options.values | Array<null | Object | number | string | boolean | Date> | optional | The values for the filter. The values are specified based on the table column the filter is being placed on and the options.operator value. |
B
mynt syntax
No Mynt syntax yet.
Nothing in the language compiles to workbook.createTableColumnFilter(options) today. How should it read?
C
community proposals
Competing syntax for createTableColumnFilter, 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?