https://netsuiteprofessionals.com logo
Join Slack
Powered by
I am seeing errors with SuiteScript 1.0 code: `nla...
# suitescript
e
I am seeing errors with SuiteScript 1.0 code: 
nlapiLoadRecord('subsidiary', subsidiaryID);
- this has worked for quite some time, but just recently starting giving me trouble (yesterday/today). Any ideas?
b
you can try sharing the error
e
Sorry! the usual unhelpful 
"code\":\"UNEXPECTED_ERROR\",\"details\":\"An unexpected SuiteScript error has occurred\",
b
but the e-fix schedule suggests an update broke your code
e
😫
that’s just wonderful news, thanks @battk - I guess I’ll have to go to Support to get more detail on that… wish there was more detail in those bullets you link to… no mention of Subsidiary or SuiteScript specific updates
Last I checked, though, 
subsidiary
is indeed a supported record…
b
depends more on the context
it could be a customization deployed to your subsidiary record
it could be that whatever value you put in subsidiaryID is invalid
or it could be permission related
lots of thing can go wrong
e
true that, but doubtful, nothing has really changed. thank you! i’ll report back, nervous about the e-fix schedule as always, thanks
b
doesnt matter if your code doesnt change, netsuite's code can change
and while it may be their fault, it can take forever to solve
you may want to do basic debugging
e
of course! I’m saying that nothing changed on our end to my knowledge… checking in with others on the team to verify that of course
i’ve been debugging, will do more thanks!
this is high priority, affects all billing (it is a script generating invoices for distribution via PDF)
Seems to be an issue in this account… can’t open a subsidiary record in edit mode at all… errors out with Unexpected Error An unexpected error has occurred. Please click here to notify support and provide your contact information.
a
do you have any scripts or workflows deployed on subsidiary records?
e
I undeployed all. there was one workflow that was part of a bundle, so i couldn’t edit, but did Suspend it as well. no dice! thanks, @amy
Waiting on NS Support now
a
bummer, hope they can resolve it!
e
turns out there was some bad reference from a Custom Other Record Field created by a bundle..? We had to deactivate. BUT, the hotfix schedule came in handy, @battk because there was actually some other issue related to the fix (PArentheses must balance)
2 Views
Open in Slack
PreviousNext
Powered by