module function · N/workbook

createSection()

workbook.createSection(options)

Creates a section.

Implementation
Not started
Design
Open for proposals suggest how it should read
Proposals
A
Signature
workbook.createSection(options)
Returns
workbook.Section
Governance
None
Script types
Server scripts
Version
SuiteScript 2.x, documented for 2.1; since NetSuite 2020.2
call shapefrom Oracle's parameter table
1workbook.createSection({2    children:  /* Array< workbook.DataDimension | workbook.CalculatedMeasure | workbook.DataMeasure | workbook.Section >, required */,3    totalLine: /* workbook.TotalLine, optional */4});
Oracle reference for this method
ParameterTypeRequiredDescription
options.childrenArray< workbook.DataDimension | workbook.CalculatedMeasure | workbook.DataMeasure | workbook.Section >requiredThe child data.
options.totalLineworkbook.TotalLineoptionalPredefined format values for the total line.
B

No Mynt syntax yet.

Nothing in the language compiles to workbook.createSection(options) today. How should it read?

C

Competing syntax for createSection, from GitHub Discussions. Select two or more to compare them side by side.

All discussions

Loading proposals from GitHub…

D

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, save and Ref[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?

N/workbook · workbook.createSection(options)

Suggest syntax for createSection