module function · N/record
delete()
record.delete(options)
Deletes a record.
- Implementation
- Implemented published in npm 0.0.1
- Design
- Accepted
delete r
A
suitescript api
1record.delete({2 type: /* string, required */,3 id: /* number | string, required */4});
| Parameter | Type | Required | Description |
|---|---|---|---|
| options.type | string | required | The record type. Use the following guidelines: When deleting an instance of a standard NetSuite record type, set this value by using the record.Type enum. When deleting an instance of a custom record type, set this value by using the custom record type's string ID. For help finding this ID, see Custom Record . |
| options.id | number | string | required | The internal ID of the record instance to be deleted. |
B
mynt syntax
Supported syntax · compiles today
1let customer = load Customer(123)2delete customer
1const customer = record.load({2 type: record.Type.CUSTOMER,3 id: 1234});5 6record.delete({7 type: record.Type.CUSTOMER,8 id: customer.id9});
Published on npm since 0.0.1. Numeric ids, as shown, since 0.1.0; 0.0.1 took the id as text, Customer("123"). Verified with mynt build on 13 Oct 2026.
C
community proposals
Competing syntax for delete, from GitHub Discussions. Select two or more to compare them side by side, with the syntax Mynt supports today as a baseline.
Mynt today
let customer = load Customer(123)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?