This site was built to compliment the existing NetSuite Professionals Slack Community by adding a means for members to easily find answers to common questions and to create a searchable database of those questions and answers.

NetSuite Professionals

Is there a reason why Object.keys(myObj).length would throw `Cannot read property 'length' of undefined` for an object that has keys?

Can you share with us the value of myObj ?

oh wait that's the value of Object.keys(myObj)

if Object.keys(myObj) is ["6", "27290", "37071"]

{6: Array(4), 27290: Array(2), 37071: Array(1)}

maybe it doesn't like numbers as properties

question. Are you sure you are passing an object and not a stringified JSON ? Numbers should work fine.

it shouldnt care unless you are doing weird stuff with prototypes or non enumerable keys

Also, are you using Suitescript 2.0 or 2.1 ? I don't know for 2.0, but I used it in 2.1 this morning, without any problems.

maybe you can just use lodash for whatever you intended

make sure `myObj` is accessible?  because `Object.keys({}).length` will return you `0` so theres no reason Object.keys() is faulty in 2.x

I figured it out. I was doing it in a for of using typescript

the error was actually from the compiled javascript of the for loop

you could use lodash instead of 'for of' or 'for in'

or &lt;insert your functional library of choice here&gt;

i love new features, but kinda feel it's too easy to mistake 'for of' and 'for in', and a functional library will have methods that better describe the semantics of what one is trying to do with the iteration

Why would load in lodash to do a simple for in loop, seems like overkill

imho, lodash should always be there. writing yet-another-loop by hand is overkill.

I can't even remember the last time I wrote a loop by hand.

..and by not writing them, I can't make mistakes with them.