mynt

module function · N/search

delete()

search.delete(options)

Deletes an existing saved search asynchronously and returns it as a search.Search object.

Implementation
Not started
Design
Open for proposals suggest how it should read
Proposals
A suitescript api
Signature
search.delete(options)
Module
N/search
Returns
void
Governance
5 units
Script types
Client and server scripts
Version
SuiteScript 2.x, documented for 2.1; since NetSuite 2015.2
call shapefrom Oracle's parameter table
1search.delete({2    id:   /* string | number, required */,3    type: /* string */4});
Oracle reference for this method
ParameterTypeRequiredDescription
options.idstring | numberrequiredInternal ID or script ID of a saved search. The script ID starts with customsearch . See Search.id for script ID. See Search.searchId for internal ID.
options.typestringThe search type of the saved search to delete. Use a value from the search.Type enum for this parameter. To successfully delete a standalone search, this parameter is required to avoid an error being thrown. For more information about standalone search types, see search.load(options) .
B mynt syntax

No Mynt syntax yet.

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

C community proposals

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

Suggest syntax for delete