https://netsuiteprofessionals.com logo
Join Slack
Powered by
```search.createFilter({ name: 'systemnotes.field'...
# suitescript
h
Copy code
search.createFilter({ name: 'systemnotes.field', etc...});
s
What exactly is the problem? 
systemnotes.field
seems like fine syntax.
b
use the join parameter of search.createFilter
s
You also need to use 
anyof
and not 
is
, hard to tell what you are doing since the whole call is not there.
h
Yes, I am using the anyof operator. For the join parameter what value gets filled there? Is it the same 'systemnotes.field' property?
Copy code
ex: search.createFilter({ name: 'systemnotes.field', join: 'systemnotes', operator: search.Operator.ANYOF, valuse: "@NONE@" });
s
Create the search in the UI and export to code, the values in there are really weird... as an example for the subsidiary field
Copy code
type: "transaction",
   filters:
   [
      ["systemnotes.field","anyof","TRANDOC.KSUBSIDIARYMAIN"]
   ],
b
You are generally confusing search filter expression syntax with the regular search filter syntax
Expressions combine both the name of the filter and it join like join.filter
Regular search filters do not and separate the join and the filter
h
in this case do you mean that the name value is the property off the join, instead of together? I.E (name: field, join: systemnotes)
s
Yes bc you are using filter and not filter expression
h
does this also apply to filters using formulas?
for example: (join: systemnotes, formula: CASE WHEN {field})
b
You would not use the join parameter when using a formula
h
whats the reason for that? do using formulas when creating filters act the same as expressions?
where the join and filter is combined?
s
You could join to multiple places in a single formula (or no join), so that syntax would be impossible to interpret
Open in Slack
PreviousNext
Powered by