mynt

module function · N/redirect

toSearchResult()

redirect.toSearchResult(options)

Redirects to search results.

Implementation
Not started
Design
Open for proposals suggest how it should read
Proposals
A suitescript api
Signature
redirect.toSearchResult(options)
Returns
void
Governance
None
Script types
afterSubmit user events
Version
SuiteScript 2.x, documented for 2.1; since NetSuite 2015.2
call shapefrom Oracle's parameter table
1redirect.toSearchResult({2    search: /* search.Search, required */3});
Oracle reference for this method
ParameterTypeRequiredDescription
options.searchsearch.SearchrequiredThe search result to be redirected to.
B mynt syntax

Not supported yet, on purpose.

Search result pages are not targets yet. The compiler lists them as not supported without naming a specific blocker. 12 Oct 2026

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

C community proposals

Competing syntax for toSearchResult, 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.toSearchResult(options)

Suggest syntax for toSearchResult