Discussions
Stay up-to-date with the latest news from NetSuite. You’ll be in the know about how to connect with peers and take your business to new heights at our virtual, in-person, on demand events, and much more.
Now is the time to ask your NetSuite-savvy friends and colleagues to join the NetSuite Support Community! Refer now! Click here to watch and learn more!
Stay in the Know
Be sure you're subscribed to NetSuite communication to stay in the know about monthly happenings, updates and announcements. Subscribe
Be sure you're subscribed to NetSuite communication to stay in the know about monthly happenings, updates and announcements. Subscribe
nlObjError quite different on client side
Anyone noticed how differently an nlobjError is on the client versus server side?
The biggest difference is the stacktrace. On the client side the stacktrace is returned as a single string (with line breaks) and on the server side it's returned as an array of Strings, one for each function call.
Additionally the information they show is different, for example on the client side you get to see the values or arguments (YES!!!) and on the server side you don't see parameter values but you see line numbers.
DoubleYouTeeEff???
This makes using these objects a real pain.
Does anyone know why they are different?
The biggest difference is the stacktrace. On the client side the stacktrace is returned as a single string (with line breaks) and on the server side it's returned as an array of Strings, one for each function call.
Additionally the information they show is different, for example on the client side you get to see the values or arguments (YES!!!) and on the server side you don't see parameter values but you see line numbers.
DoubleYouTeeEff???
This makes using these objects a real pain.
Does anyone know why they are different?
Steve Klett | Senior Developer
NetValue Technology
0