module function · N/action
execute()
action.execute(options)
Executes the record action and returns action results in an object.
- Implementation
- Not started
- Design
- Open for proposals suggest how it should read
A
suitescript api
1action.execute({2 recordType: /* string, required */,3 id: /* string, required */,4 params: /* Object, required */5});
| Parameter | Type | Required | Description |
|---|---|---|---|
| options.recordType | string | required | The record type. For a list of record types, see record.Type . |
| options.id | string | required | The action ID. For a list of action IDs, see Supported Record Actions . |
| options.params | Object | required | Action arguments. |
| options.params.recordId | int | required | The record instance ID. This is the NetSuite record internal ID. |
B
mynt syntax
No Mynt syntax yet.
Nothing in the language compiles to action.execute(options) today. How should it read?
C
community proposals
Competing syntax for execute, 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?