module function · N/dataset
create()
dataset.create(options)
Creates a dataset.
- Implementation
- Not started
- Design
- Open for proposals suggest how it should read
A
suitescript api
1dataset.create({2 columns: /* dataset.Column [], optional */,3 condition: /* dataset.Condition, optional */,4 description: /* string, optional */,5 id: /* string, optional */,6 name: /* string, optional */,7 type: /* string, required */8});| Parameter | Type | Required | Description |
|---|---|---|---|
| options.columns | dataset.Column [] | optional | The fields (columns) in the dataset. |
| options.condition | dataset.Condition | optional | The condition (criteria to be applied to the dataset. A condition can have children which are combined using the appropriate operator (AND or OR) to produce the criteria used. |
| options.description | string | optional | The description of the dataset. |
| options.id | string | optional | The script ID of the dataset. |
| options.name | string | optional | The name of the dataset. |
| options.type | string | required | The internal ID for the record type on which to build the dataset. Use the Records Catalog to find the Internal ID of scriptable records. |
B
mynt syntax
No Mynt syntax yet.
Nothing in the language compiles to dataset.create(options) today. How should it read?
C
community proposals
Competing syntax for create, 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?