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

check out array.filter or if you want something even fancier lodash has some methods exactly for this type of thing

array.filter is what i was planning on using. i'm tripped up on it.

for filter the first parameter is a function

the function has 3 parameters, the current element, the index, and the array itself

the function is supposed to return true if you want to keep the element

the return value of filter is an array of elements that had true returned

if you are implementing a uniqueness function, you need to keep track of which emails you have already added, and return false if you already processed that email

Untitled

like so? i can normally get by with just elem and indexOf

unless someone wants to show me a better way

formal computer science says your solution is O(n^2)

ya, i can see that. lol keep looking i guess

its most likely never going to matter w/ the data sets in netsuite

i was steering you towards using an object to keep track of which emails you added

that said, im with <@U2C4P9YR3>, it doesnt matter unless you start hundreds of thousands of elements

of course. i shouldn't have cluttered up the array in the first place lol

tens of thousands might have measurable impact, but thats more rhino is slow

yeah even if you have an O(n) who knows how rhino does it

It would have to be an obscene amount of records to matter so it doesn't really.. if 10s of thousands probably wouldn't matter you'd need a ton before you'd see any NOTICEABLE slowdown

on paper, sure there's a difference but in real world for this its so tiny

Here's a much more compact method if you're able to use SS2.1:
```data.filter((el, i) =&gt; data.map(obj =&gt; obj.email).indexOf(el.email) === i);```

I'm not, at the moment. 2.1 broke email logging for me on records when you specify a relatedRecord when sending an email. As far as I know it's an ongoing issue.

if you are concerned about performance,  keep track of emails that have been seen already

if its not a concern, leave it as is, your implementation is fine

if you are paranoid, use lodash, or at least look at how lodash does it