setWhenOrderedBy: A Warning

Have you tried using setWhenOrderedBy in some 2.0 code recently?

If you have, it was probably extremely frustrating. This has come up quite a few times recently, so I wanted to issue a warning:

There seem to be some significant bugs with the setWhenOrderedBy API in SuiteScript 2.0.

If you’ve gotten it to work correctly, I’d love it if you could share your working example.

If you need to use setWhenOrderedBy but it’s just not working, you have a few alternatives, but none of them are great:

  • Isolate the setWhenOrderedBy part of your functionality into a separate Script and use 1.0 for it; as far as I know the 1.0 version of the API works just fine
  • Try loading a Saved Search instead of creating it in script to see if that bypasses the bug. I’m not sure if this actually works.
  • Remove the setWhenOrderedBy portion of your search and do that grouping and sorting yourself. I recommend a utility library like lodash or ramda for this as they both provide excellent array manipulation methods.
{"email":"Email address invalid","url":"Website address invalid","required":"Required field missing"}

Related posts

January 7, 2021

Anything I wrote today about business would both feel and be inadequate. I simply can’t arrive at the words to express how I feel in this moment. So instead, here are a few helpful ...

Read More

December 20, 2020

2020 was a hundred swift kicks to the shorts and one giant kick in the ass. If you’ve lost people you love, if you’ve gotten sick or hurt, if you’ve lost your job, if ...

Read More

December 16, 2020

“I’ve been meaning to learn SuiteScript, but it’s hard to find the time …”“We’re slammed, and I just don’t have the time …”“I haven’t made the time …” All are variations of a theme ...

Read More

December 14, 2020

Last week we looked at mimicking the functionality of a REST endpoint with its own module (e.g. retrieving a User, or a list of Users, refreshing a token, etc). For complex integrations that rely on a large ...

Read More