Hi all, just a curious question. Does anyone have a framework/pattern when making 'search' API calls? I've got a few I could share, just wondered if anyone else has come up with any?

Not 100% sure what you're looking for, but I do my best not to abstract the search API too far. That said, there are a few things I do very consistently: 1. Nearly all my searches leverage Filter Expressions and string-based Column names (as opposed to using

createColumn()

and

createFilter()

2. Almost every search is encapsulated in its own function named

find*

(e.g.

findOrders

) and looks very much like:

s.create(...)
  .run()
  .getRange(...)
  .map(resultToObject);

That's preciously where I'm at right now ... was asking the community to see if there was something I hadn't thought of yet.

I agree with the above approach as well, generally what we use. we have dabbled in creating a wrapper around search functionality with base "class" and extending from there etc. to mess with OOP and inheritance but generally does not seem worth the overhead. but I guess it depends on the scope of your project and what someone could potentially gain from additional framework

umm, running searches is such a common case it's part of NFT https://github.com/ExploreConsulting/netsuite-fasttrack-toolkit-ss2#lazy-search

Here's how I've been handling that. This is part of a RESTlet that provides access to customer data. The call to the RESTlet can include an array of filters to be applied to the search, and an array of columns to be returned. So it's very flexible.