module function · N/workbook
createSort()
workbook.createSort(options)
Creates a sort.
- Implementation
- Not started
- Design
- Open for proposals suggest how it should read
A
suitescript api
1workbook.createSort({2 ascending: /* boolean, optional */,3 caseSensitive: /* boolean, optional */,4 locale: /* query.SortLocale, optional */,5 nullsLast: /* boolean, optional */6});
| Parameter | Type | Required | Description |
|---|---|---|---|
| options.ascending | boolean | optional | Indicator for sorting in ascending order. If set to false, sorting is done in descending order. The default value is true (sort in ascending order). |
| options.caseSensitive | boolean | optional | Indicator that the sort should consider case sensitivity. |
| options.locale | query.SortLocale | optional | The option for locale specific sorting. |
| options.nullsLast | boolean | optional | Indicator that the sort should place null items last. The default of this parameter is the value of the ascending parameter (for example, if options.ascending is set to false, the default for this parameter will be false). |
B
mynt syntax
No Mynt syntax yet.
Nothing in the language compiles to workbook.createSort(options) today. How should it read?
C
community proposals
Competing syntax for createSort, 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?