module function · N/workbook
createCategory()
workbook.createCategory(options)
Creates a chart category, which includes an axis, a data root, and a sort definition.
- Implementation
- Not started
- Design
- Open for proposals suggest how it should read
A
suitescript api
1workbook.createCategory({2 axis: /* workbook.ChartAxis, required */,3 root: /* workbook.DataDimension | workbook.Section, required */,4 sortDefinitions: /* workbook.SortDefinition [], optional */5});
| Parameter | Type | Required | Description |
|---|---|---|---|
| options.axis | workbook.ChartAxis | required | The chart category axis definition. |
| options.root | workbook.DataDimension | workbook.Section | required | The data that feeds the chart category. |
| options.sortDefinitions | workbook.SortDefinition [] | optional | The sorting for the chart category. |
B
mynt syntax
No Mynt syntax yet.
Nothing in the language compiles to workbook.createCategory(options) today. How should it read?
C
community proposals
Competing syntax for createCategory, 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?