N/runtime

is not implemented for client script deployments on Time (i.e.,

timebill

or

record.Type.TIME_BILL

). A script that uses this module didn't work as expected when I deployed it on

timebill

. I used

log.debug

to record the state of the script context and runtime objects to the log. The runtime object was empty:

{}

. Is this a bug or is it intentional? In other words, did the SS2 team fail to implement

N/runtime

on

timebill

, or is it intentional? I have a hard time understanding how or why it could be intentional. Even if the context is always the UI, the other runtime attributes are variable. Does anyone know what is going on here? Is this issue discussed in the documentation?

you might want to ask in #C29HQS63G. But N/runtime should work fine in clientscript Dont expect log.debug to log anything useful for N/runtime, log.debug will use the toJSON method on the runtime object to log use console.log(runtime) if you want to log something more useful

oops! I thought I was posting to SuiteScript. And you're right, BTW `Object.getOwnPropertyNames`returns all the prop names, so the problem has to be in the logic (I'm expected the context type to be one thing, but it's another0.