Can anyone shed any light as to why the below would not work NetSuite Professionals #suitescript

Can anyone shed any light as to why the below woul...

karlenigma

04/25/2018, 4:00 PM

Can anyone shed any light as to why the below would not work on a UE BeforeSubmit? Works in a client script.

Copy code

var searchResults = search.create({
                         type: "salesorder",
                         filters: [["name","anyof",custIntID], "AND", ["item","anyof",itemIntID], "AND", ["type","anyof","SalesOrd"], "AND", ["closed","is","F"]],
                         columns: [search.createColumn({name: "trandate", sort: search.Sort.DESC}), "rate"]}).run().getRange({start:0, end: 1});

jkabot

04/25/2018, 9:20 PM

variables

custIntID

and/or

itemIntID

are likely numbers instead of strings. In my experience search filter expressions only play nice with strings. It works in the client because in the client

search.create

is implemented differently. It delegates the search to a script handler endpoint via an http request. The http request probably converts all parameters to strings.

eminero

04/26/2018, 3:33 AM

What is the error you are getting?

karlenigma

04/26/2018, 7:17 AM

{"type":"error.SuiteScriptError","name":"SSS_INVALID_SRCH_OPERATOR","message":"An nlobjSearchFilter contains an invalid operator, or is not in proper syntax: item."

karlenigma

04/26/2018, 7:40 AM

@jkabot I get what your saying but i must be getting the wrong value from my itemIntID variable.

jkabot

04/26/2018, 3:51 PM

You can log the value and also log

typeof itemIntId

jkabot

04/26/2018, 3:51 PM

The suitescript 2.0 api is really inconsistent in terms of when it returns a string or an number for internalids

jkabot

04/26/2018, 3:52 PM

You might be able to fix it by using

String(itemIntId)

karlenigma

04/26/2018, 3:54 PM

Yeah i think it is because another function not working correctly wither.

Open in Slack

Previous Next