What about Number() instead of parseInt()
# suitescripta
alien4u
05/13/2022, 5:56 PMWhat about Number() instead of parseInt()
c
Cory Weiner
05/13/2022, 5:58 PMNumber gives the same error. Oddly though this works:
Copy code
Number(data.id).toString()a
alien4u
05/13/2022, 6:00 PMThen that data.id is coming with some weird character that you don't even see, Number() would get rid of that and toString() is going to normalize it...
alien4u
05/13/2022, 6:00 PMIt should work with string without any problem.
c
Cory Weiner
05/13/2022, 6:01 PMWhat character could there possibly be? Number() yields NaN for any non numeric character AFAIK
a
alien4u
05/13/2022, 6:02 PMconsole.log(Number('12345 '))
alien4u
05/13/2022, 6:02 PMconsole.log(Number('12345 \n'))
alien4u
05/13/2022, 6:03 PMconsole.log(Number('12345 \r'))
c
Cory Weiner
05/13/2022, 6:03 PMI see, but the output of that is still 12345 as an integer. Why would toString() be needed?
a
alien4u
05/13/2022, 6:04 PMoptions.id number | string | required | The internal ID of the existing record instance in NetSuite.
alien4u
05/13/2022, 6:05 PM15011.0 this is not the same as the output of Number... if Number() output is 15011 and still errors out, then is just because it is NetSuite...
alien4u
05/13/2022, 6:06 PMI would take Number() over parseInt() any day...
💯 1
c
Cory Weiner
05/13/2022, 6:07 PMSure no problem with using Number() but it’s odd that that the output of that still gives the error. I’ll chalk it up to a netsuite bug.
a
alien4u
05/13/2022, 6:09 PMThis is one of the reason I don't like parseInt:
console.log(parseInt(0.05)) // 0
console.log(parseInt(0.005)) // 0
console.log(parseInt(0.0000005)) // 5
On top of that you would face radix issues too if you don't specific the radix.
c
Cory Weiner
05/13/2022, 6:11 PMGood to know. Thanks
s
Shawn Talbert
05/13/2022, 8:20 PMI tend to avoid
submitFields6 Views