mynt

module function · N/redirect

toSavedSearch()

redirect.toSavedSearch(options)

Redirects to a saved search.

Implementation
Not started
Design
Open for proposals suggest how it should read
Proposals
A suitescript api
Signature
redirect.toSavedSearch(options)
Returns
void
Governance
5 units
Script types
afterSubmit user events
Version
SuiteScript 2.x, documented for 2.1; since NetSuite 2015.2
call shapefrom Oracle's parameter table
1redirect.toSavedSearch({2    id: /* number, required */3});
Oracle reference for this method
ParameterTypeRequiredDescription
options.idnumberrequiredInternal ID of the search. The internal ID is available only when the search is either loaded with search.load(options) or after is has been saved with Search.save() . Typical values are 55 or 234 or 87, not a value like customsearch_mysearch . Any ID prefixed with customsearch is a script ID, not the internal system ID for a search.
B mynt syntax

Not supported yet, on purpose.

redirect Search("customsearch_x") is refused. toSavedSearch takes a saved search's numeric internal id, while Mynt names saved searches by script id, and resolving one would hide a search.load inside the redirect. 12 Oct 2026

It stays open for proposals: a design that resolves this is welcome.

C community proposals

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

Suggest syntax for toSavedSearch