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

March 3, 2021

Does the physical location of a competent employee change the amount of value they can deliver for your organization? If it does, I’d be keen to hear your story. If it does not, why ...

Read More

March 2, 2021

Today a friend and former colleague of mine – who happens to now be in a development leadership role for a NetSuite partner – was lamenting the extreme difficulty of finding and hiring NetSuite ...

Read More

March 1, 2021

Software is never finished; clients are always changing and re-prioritizing. NetSuite is ever a moving target – always updating and evolving. Market forces are always shifting and shoving, forcing new demands on your business. ...

Read More