Dataset object method · N/dataset

save()

Dataset.save(options)

Saves a dataset.

Implementation
Not started
Design
Open for proposals suggest how it should read
Proposals
A
Signature
Dataset.save(options)
Module
N/dataset
Returns
Object
Governance
10
Script types
Server scripts
Version
SuiteScript 2.x, documented for 2.1; since NetSuite 2020.2
call shapefrom Oracle's parameter table
1objDataset.save({2    name:        /* string | workbook.Expression, required */,3    description: /* string | workbook.Expression, optional */,4    id:          /* string, optional */5});
Oracle reference for this method
ParameterTypeRequiredDescription
options.namestring | workbook.ExpressionrequiredThe name of the dataset.
options.descriptionstring | workbook.ExpressionoptionalThe description of the dataset.
options.idstringoptionalThe ID of the dataset.
B

No Mynt syntax yet.

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

C

Competing syntax for save, 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/dataset · Dataset.save(options)

Suggest syntax for save