module function · N/workbook

createConditionalFilter()

workbook.createConditionalFilter(options)

Creates a conditional filter.

Implementation
Not started
Design
Open for proposals suggest how it should read
Proposals
A
Signature
workbook.createConditionalFilter(options)
Returns
workbook.ConditionalFilter
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.createConditionalFilter({2    measure:   /* workbook.CalculatedMeasure | workbook.DataMeasure, required */,3    predicate: /* workbook.Expression, required */,4    row:       /* boolean, required */5});
Oracle reference for this method
ParameterTypeRequiredDescription
options.measureworkbook.CalculatedMeasure | workbook.DataMeasurerequiredThe measure for the conditional filter.
options.predicateworkbook.ExpressionrequiredThe predicate for the conditional filter.
options.rowbooleanrequiredIndicator for a row axis filter. If set to false, the filter is a on a column axis.
B

No Mynt syntax yet.

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

C

Competing syntax for createConditionalFilter, 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.createConditionalFilter(options)

Suggest syntax for createConditionalFilter