mynt

module function · N/config

load()

config.load(options)

Loads a record.Record object that encapsulates the specified configuration page.

Implementation
Not started
Design
Open for proposals suggest how it should read
Proposals
A suitescript api
Signature
config.load(options)
Module
N/config
Returns
record.Record
Governance
10 units
Script types
Server scripts
Version
SuiteScript 2.x, documented for 2.1; since NetSuite 2015.2
call shapefrom Oracle's parameter table
config.load(options.type /* enum, required */, options.isDynamic /* boolean, optional */, INVALID_RCRD_TYPE /* The record type {type} is invalid. */);
Oracle reference for this method
ParameterTypeRequiredDescription
options.typeenumrequiredThe NetSuite configuration page you want to access. Use the config.Type enum to set the value.
options.isDynamicbooleanoptionalDetermines whether the record is loaded in dynamic mode. If set to true , the record is loaded in dynamic mode. If set to false , the record is loaded in standard mode. For more information, see SuiteScript 2.x Standard and Dynamic Modes .
INVALID_RCRD_TYPEThe record type {type} is invalid.
B mynt syntax

No Mynt syntax yet.

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

C community proposals

Competing syntax for load, from GitHub Discussions. Select two or more to compare them side by side.

All discussions

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/config · config.load(options)

Suggest syntax for load