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
A
suitescript api
1url.resolveRecord({2 isEditMode: /* boolean, required */,3 recordId: /* string | number, required */,4 recordType: /* string, required */,5 params: /* Object, optional */6});
| Parameter | Type | Required | Description |
|---|---|---|---|
| options.isEditMode | boolean | required | If 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.recordId | string | number | required | The record ID of the target record instance. |
| options.recordType | string | required | The type of record. For example, 'purchaseorder'. |
| options.params | Object | optional | Object used to add parameters for a custom URL. For example, a query to a database or to a search engine. |
B
mynt syntax
No Mynt syntax yet.
Nothing in the language compiles to url.resolveRecord(options) today. How should it read?
C
community proposals
Competing syntax for resolveRecord, from GitHub Discussions. Select two or more to compare them side by side.
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,saveandRef[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?