module function · N/record

submitFields()

record.submitFields(options)

Updates and submits one or more body fields on an existing record in NetSuite, and returns the internal ID of the parent record.

Implementation
Not started
Design
Open for proposals suggest how it should read
Proposals
A
Signature
record.submitFields(options)
Module
N/record
Returns
Object
Governance
Transaction records: 10 units Custom records: 2 units All other records: 5 units
Script types
Client and server scripts
Version
SuiteScript 2.x, documented for 2.1; since NetSuite 2015.2
call shapefrom Oracle's parameter table
1record.submitFields({2    type:    /* string, required */,3    id:      /* number | string, required */,4    values:  /* Object, required */,5    options: /* Object, optional */6});
Oracle reference for this method
ParameterTypeRequiredDescription
options.typestringrequiredThe record type. Use the following guidelines: When working with an instance of a standard NetSuite record type, set this value by using the record.Type enum. When working with 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.idnumber | stringrequiredThe internal ID of the existing record instance in NetSuite.
options.valuesObjectrequiredThe ID-value pairs for each field you want to edit and submit. The value type must correspond to the field type being set. For example: Text, Radio, Select and Multi-Select fields accept string values. Checkbox fields accept boolean values. Date and DateTime fields accept Date values. Integer, Float, Currency and Percent fields accept number values.
options.optionsObjectoptionalAdditional options to set for the record.
B

No Mynt syntax yet.

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

C

Competing syntax for submitFields, 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/record · record.submitFields(options)

Suggest syntax for submitFields