This site was built to compliment the existing NetSuite Professionals Slack Community by adding a means for members to easily find answers to common questions and to create a searchable database of those questions and answers.

NetSuite Professionals

```items.forEach(function (item) {
            log.debug('Item Sku' , item.sku)
            search.create(
                {type:'item', filters: [['itemid', 'is', item.sku]]
               }).run().each(function(result){
                log.debug('Result ID: ', result.id)
              });

}```

yeah its possible and it's also terribly inefficient

I am Passing a whole order with all the Line_items which is an array that holds each item as an object

Agree it is inefficient. If it’s a small operation, it might be fine so depends on what you’re doing. If you’re doing thousands of iterations, it’s going to be very slow and you’ll likely run into governance limits.

But, the reason you’re only getting 1 result is that you’re not returning true from your each() function. If you don’t return true, it will stop after 1 iteration.

:thumbsup:  what is a more efficient way of doing this task?

Most likely an order will not have more than 20 skus

What type of script will this be on? UserEvent, ScheduledScript?

I have a Nodejs that will call it and send data back and forth

You might consider if you could load up the item data you need in cache using the N/cache module. That way, you’re not hitting the DB on each call. If you need realtime data like qty on hand, that might not work.

you can pass an array into the search criteria, like `[item, 'anyof', idArray]` and do a single search and process the results

Ok I will look into these suggestions, thank you

<@U02KBHMD137> You may be better off running a transaction search and then adding joins to the item fields you need in the search. So then you are returning the order as a search with the extra fields and not looping the lines and doing a lookup on each line. It is way faster. Or even turning that search into a sql query would be much faster.

Use the N/query to get the line data you need before the loop. Significantly faster than N/search. Also, the cache idea above is a great one if you're calling the same order several times within a few minutes.

So <@U37NQCPM0> when is the chrome extension for N/query module coming out? :wink:
It cause of your extension that I have a hard time moving away from N/search

I released it before SW. Keep in mind it's BETA. One thing I've noticed and haven't fixed is that you have to refresh the page after selecting the workbook for the button to show up.

There was actually one previously released by someone else but for some reason it was removed from the chrome store

:thumbsup: This was very challenging to get SS2.0 into the extension. Hopefully it works ok...