module function · N/workbook
createDataMeasure()
workbook.createDataMeasure(options)
Creates a data measure.
- Implementation
- Not started
- Design
- Open for proposals suggest how it should read
A
suitescript api
1workbook.createDataMeasure({2 aggregation: /* workbook.Aggregation, required */,3 expression: /* workbook.Expression */,4 expressions: /* workbook.Expression [] */,5 label: /* string | workbook.Expression, optional */6});| Parameter | Type | Required | Description |
|---|---|---|---|
| options.aggregation | workbook.Aggregation | required | The type of aggregation to use for the data measure. |
| options.expression | workbook.Expression | The expression for the data measure (if the data measure is a single-expression measure). | |
| options.expressions | workbook.Expression [] | The expressions for the data measure (if the data measure is a multi-expression measure). | |
| options.label | string | workbook.Expression | optional | The label for the data measure. |
B
mynt syntax
No Mynt syntax yet.
Nothing in the language compiles to workbook.createDataMeasure(options) today. How should it read?
C
community proposals
Competing syntax for createDataMeasure, 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?