module function · N/workbook
createMeasureValueSelector()
workbook.createMeasureValueSelector(options)
Creates a measure value selector.
- Implementation
- Not started
- Design
- Open for proposals suggest how it should read
A
suitescript api
1workbook.createMeasureValueSelector({2 columnSelector: /* workbook.DescendantorSelfNodesSelector | workbook.DimensionSelector | workbook.PathSelector, required */,3 rowSelector: /* workbook.DescendantorSelfNodesSelector | workbook.DimensionSelector | workbook.PathSelector, required */4});| Parameter | Type | Required | Description |
|---|---|---|---|
| options.columnSelector | workbook.DescendantorSelfNodesSelector | workbook.DimensionSelector | workbook.PathSelector | required | The column to style. |
| options.rowSelector | workbook.DescendantorSelfNodesSelector | workbook.DimensionSelector | workbook.PathSelector | required | The row to style. |
B
mynt syntax
No Mynt syntax yet.
Nothing in the language compiles to workbook.createMeasureValueSelector(options) today. How should it read?
C
community proposals
Competing syntax for createMeasureValueSelector, 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?