module function · N/workbook
createDataDimension()
workbook.createDataDimension(options)
Creates a data dimension.
- Implementation
- Not started
- Design
- Open for proposals suggest how it should read
A
suitescript api
1workbook.createDataDimension({2 children: /* Array< workbook.DataDimension | workbook.Section | workbook.CalculatedMeasure | workbook.DataMeasure >, optional */,3 items: /* workbook.DataDimensionItem [], required */,4 totalLine: /* workbook.TotalLine, optional */5});| Parameter | Type | Required | Description |
|---|---|---|---|
| options.children | Array< workbook.DataDimension | workbook.Section | workbook.CalculatedMeasure | workbook.DataMeasure > | optional | The child data dimensions or sections of the data dimension. |
| options.items | workbook.DataDimensionItem [] | required | The items of the data dimension. |
| options.totalLine | workbook.TotalLine | optional | The predefined formats for the total line. |
B
mynt syntax
No Mynt syntax yet.
Nothing in the language compiles to workbook.createDataDimension(options) today. How should it read?
C
community proposals
Competing syntax for createDataDimension, 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?