Or show the line relevant data in the alert...

You could. Depending on how many duplicates and whether or not there's enough info to let the user know.

if you've got 2 duplicate lines though, you gotta be able to let them know which is the duplicate.. so if you had a suitelet that they could redirect to that just displayed the duplicate lines and you picked which one to remove that could be way more friendly and isn't that much work

Just throwing out additional ideas you can go w/ whatever works best for you

Thanks...

I will see because at the end is only informational they can decide to go and enter it duplicated...

how do you even get duplicate lines on sales orders

like is the automation just goofing up or are people making lots of errors

ahh 🤦 why is suiteanswers filled with code samples that look like this

var initValues = new Array();
initValues.grouptype = 'Employee';
initValues.dynamic = 'F';

@creece People create Sales Order Importing CSV files, it could be 500 lines... then 2 weeks later they need to manually add few items... then they could by mistake try to add an item is already there...

Ok right now I think I can use that very same question about script parameters from this morning...

I have a Suitelet which trigger a Map Reduce... if the Suitelet is use again before the Map Reduce ends I got an error because that map reduce is already running...

In the second execution of the Suitelet I don't have the taskID I execute on the first execution... to trigger a second deployment... any idea with this?

is your goal is to trigger a second deployment of the map/reduce script?

yeah if the first one is in use...

you can just omit the deployment when you call

task.create

and it will use the first available deployment.

Oh that is even better... thanks...

if all deployments are taken up you'll still get that error though

so you'll need a do/while loop to keep checking

Maybe a suitelet parameter to store the last taskID execute and then check with that on each run...?

You know there's an error thrown, so you can keep trying until there is no error

like you can pause for 5 secs and retry or something or limit your retries etc...

how do you pause in a server script

you can fake lots of things

setTimeout is not available

do you need to busy-wait?

Got you @creece getting the Map Reduce call inside a try catch and from there re-try... that also good...

Thanks,...

@creece uploaded a file: Untitled

unless its like perpetually stuck in error it should work or it'll time out