mynt

Record object method · N/record

getValue()

Record.getValue(options)

Returns the value of a field.

Implementation
Implemented published in npm 0.0.1
Design
Accepted r.field
Proposals
A suitescript api
Signature
Record.getValue(options)
Module
N/record
Returns
number | Date | string | array | boolean
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.getValue({2    fieldId: /* string, required */3});
Oracle reference for this method
ParameterTypeRequiredDescription
options.fieldIdstringrequiredThe internal ID of a standard or custom body field. See, Finding Internal IDs of Record Fields .
B mynt syntax

Supported syntax · compiles today

myntr.field
log.debug(customer.comments)
suitescriptoutput, trimmed
1log.debug({2    title: "execute",3    details: customer.getValue({4        fieldId: "comments"5    })6});

Published on npm since 0.0.1. Verified with mynt build on 13 Oct 2026.

C community proposals

Competing syntax for getValue, 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 todaylog.debug(customer.comments)

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

Suggest syntax for getValue