@alien4u I'm talking about the "BLOCKED BY XSS AUDITOR" error specifically, scripts we had running fine for over 6 months suddenly tripped this

I did turn off the script and stop seeing the error though

@Nelli I saw someone else on this thread suggest that a few days back. I got this error only one time on chrome and it was something in my code that broke with the 2018.1 upgrade. Adjusting my code fixed it. But i saw someone comment a few days back that they were using FF as a workaround...

@Nelli I understand... but I have near 100 or maybe more scripts running... and 80 Users... and no error...

@alien4u @jacksonp Exactly, it is rare and sporadic. Not entirely sure what is causing it. in my case, 2018.1 upgrade was causing it and the solution was to add one filter to a saved search in my code...

It's a pain right now. I've definitely run into this error several times though. Adjusting the scripts typically fixes it

I was hoping someone had more insight

i got the clue to add a filter to fix my issue from NS support. So best to contact them...

@jacksonp I think I see your problem...

oh?

OK so if adding a filter fixed it or others have adjusted their code to fix it, maybe share what exactly you did to help others?

You are passing an array to your search which have an object inside...

Try to only pass an array to the search...

Alright I'll try it

also the error happened before the search part was created. We just had to make a change to the script, that added the search to it

You are passing now [{}]... try only with [id,id2,id3]

Okay, I made the change, let me test it real quick

Critiques welcome

Alright @alien4u I tested saving the record 3 times, and that seemed to fix it

Thanks!

Is there a way to deploy scheduled scripts for testing on demand?

@iSuite yes leave it "Not Scheduled" then when you want to run it hit edit and from the Save button use the drop down to do Save and Execute

A file was commented on

whats going to be the best way of deleting a lot of custom record entries via scheduled script? there are about 2m entries and doing a foreach and record.delete i get about 2500 out before the usage limit is exceeded

does it have to be a scheduled script?

Could do a Map / Reduce

if so, our typical code looks like this

lazy.createSearch(...search criteria for delete)
.takewhile(governanceRemains)
.each(... do stuff)

and the function

governanceRemains

just checks that say 200 units remain and if not it reschedules the script and returns false. This provides a very clean exit and works with an arbitrarily large number of search results.

Hi, recently I've been playing with unit testing and I've wondered, what do you guys use to unit test your netsuite developments? Do you have any site/course that you recommend about this subject?

@thatguymikeneal You should be able to do a Mass Update script to handle that and your code would be 1 line...

it needs to be something scheduled just so it can constantly clear off old records