module function · N/url

resolveRecord()

url.resolveRecord(options)

Returns an internal URL to a NetSuite record.

Implementation
Not started
Design
Open for proposals suggest how it should read
Proposals
A
Signature
url.resolveRecord(options)
Module
N/url
Returns
string
Governance
None
Script types
Client and server scripts
Version
SuiteScript 2.x, documented for 2.1; since NetSuite 2015.1
call shapefrom Oracle's parameter table
1url.resolveRecord({2    isEditMode: /* boolean, required */,3    recordId:   /* string | number, required */,4    recordType: /* string, required */,5    params:     /* Object, optional */6});
Oracle reference for this method
ParameterTypeRequiredDescription
options.isEditModebooleanrequiredIf set to true , returns a URL for the record in Edit mode. If set to false , returns a URL for the record in View mode The default value is View .
options.recordIdstring | numberrequiredThe record ID of the target record instance.
options.recordTypestringrequiredThe type of record. For example, 'purchaseorder'.
options.paramsObjectoptionalObject used to add parameters for a custom URL. For example, a query to a database or to a search engine.
B

No Mynt syntax yet.

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

C

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

Suggest syntax for resolveRecord