i'm tempted to try record.create on a deployment record and see what sort of field values i can set

Let say I have a Suitelet in use by 5 peoples... each one when process the data fire de Map Reduce but some of them will just get an error saying Map Reduce already running?

@creece uploaded a file: Untitled

maybe give that a go i've never seen it done

worth investigating at least

seems a bit odd to do that though .. the alt path appears to be the more "normal" path

@creece Thanks, I already have it running like that... that code indeed work for me... the problem is when the Map Reduce is already running?

you could trap the status and do a do/while maybe but there's 20 governance per submit

The only thing I'm thinking about is have 5 deployments for that M/R and then check if is running fire the available one...

share those 5 deployment and loop throught them and fire the one free/non-running...

its 0 governance to create a task and check the status

perfect that should work then I will try that...

that doesn't really fix your error though if none are available

you'd have to do some kind of do/while loop that continuously checks until ones available but that'll hold up the process

or depending on what @al3xicon finds out, you may be able to just dynamically create a deployment and let it go

yeah, it'd be sweet, but i'd be surprised

i'll likely be testing that later this week and will keep y'all posted

All because we don’t have the concept of a task queue available in suitescript

it would be so cool to have one. It’d definitely help for things like performance. All integrations that push data elsewhere on after submit…

A client has a need to send an email with a blank subject (i.e. not a space, but an empty string). NS doesn't like that (says "Missing a required argument: options.subject" using email.send in 2.0). Anyone have any ideas for how to make the subject empty while making NS think it's not?

@pablod what I've done is stuck the logic in a Workflow Action Script, and then triggered the workflow asynchronously

But I'm strongly considering converting it to a scheduled script and implementing my own queue to take advantage of the extra processor available on 2018.1

@michoel I believe you wanted to talk with the other Pablo @PabloZ 🙂

Whoops thanks

how do you trigger the wf?

thanks @michoel! I wasn’t aware of that one.

I'm unable to inline edit a custom checkbox on a PO using `record.submitFields`; I've tried both

"T"

and

true

as the field value, but neither has any effect. Suggestions?

This is from a Suitelet. Using

"T"

works fine from console.

Hm, can't even

load.setValue.save

it from the Suitelet either