module function · N/workbook
createSortByMeasure()
workbook.createSortByMeasure(options)
Creates a sort based on a measure.
- Implementation
- Not started
- Design
- Open for proposals suggest how it should read
A
suitescript api
1workbook.createSortByMeasure({2 measure: /* workbook.CalculatedMeasure | workbook.DataMeasure, required */,3 selector: /* Array< workbook.DescendantorSelfNodesSelector | workbook.DimensionSelector | workbook.PathSelector >, required */,4 sort: /* workbook.Sort, required */5});| Parameter | Type | Required | Description |
|---|---|---|---|
| options.measure | workbook.CalculatedMeasure | workbook.DataMeasure | required | The measure to sort by. |
| options.selector | Array< workbook.DescendantorSelfNodesSelector | workbook.DimensionSelector | workbook.PathSelector > | required | The selector for the sort. |
| options.sort | workbook.Sort | required | The sort used to create. |
B
mynt syntax
No Mynt syntax yet.
Nothing in the language compiles to workbook.createSortByMeasure(options) today. How should it read?
C
community proposals
Competing syntax for createSortByMeasure, 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?