mynt

Record object method · N/record

setValue()

Record.setValue(options)

Sets the value of a field.

Implementation
Implemented published in npm 0.0.1
Design
Accepted r.field = value
Proposals
A suitescript api
Signature
Record.setValue(options)
Module
N/record
Returns
record.Record
Governance
None
Script types
Client and server scripts
Version
SuiteScript 2.x, documented for 2.1; since NetSuite 2015.2
call shapefrom Oracle's parameter table
1objRecord.setValue({2    fieldId: /* string, required */,3    value:   /* number | Date | string | array | boolean, required */4});
Oracle reference for this method
ParameterTypeRequiredDescription
options.fieldIdstringrequiredThe internal ID of a standard or custom body field. See, Finding Internal IDs of Record Fields .
options.valuenumber | Date | string | array | booleanrequiredThe value to set the field to. The value type must correspond to the field type being set. For example: Text and Radio fields accept string values. Select fields accept string and number values. Multi-Select fields accept arrays of string or number values. Checkbox fields accept boolean values. Date and DateTime fields accept Date values. Integer, Float, Currency and Percent fields accept number values. Inline HTML fields accept strings. Strings containing HTML tags are represented as HTML entities in UI, this is demonstrated in Syntax section below. For rate and ratehighprecisionfields, use the Record.setText(options) method to set a string value with a "%". For more information, see Record.setText(options) .
B mynt syntax

Supported syntax · compiles today

myntr.field = value
customer.comments = "Reviewed"
suitescriptoutput, trimmed
1customer.setValue({2    fieldId: "comments",3    value: "Reviewed"4});

Read-only fields and type mismatches are compile errors. Published on npm since 0.0.1. Verified with mynt build on 13 Oct 2026.

C community proposals

Competing syntax for setValue, from GitHub Discussions. Select two or more to compare them side by side, with the syntax Mynt supports today as a baseline.

All discussions
Mynt todaycustomer.comments = "Reviewed"

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, 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.setValue(options)

Suggest syntax for setValue