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.
New AI Community Guidelines. Please review and follow them to ensure AI use stays safe, accurate, and compliant.
Keep an eye out for upcoming NetSuite events, including meetups, workshops, and webinars. These sessions are a great way to connect with peers, learn from experts, and stay current on the latest NetSuite updates and best practices. Registration links are provided in each event.
Save $30 - limited to first 1,000 registrants
Join the NetSuite community to innovate, connect, and discover what’s next.
SuiteWorld brings thousands of innovators, builders, and leaders together to learn, connect, and shape what’s next. This October, explore how to build a stronger foundation for growth through inspiring keynotes, major product reveals, hands-on sessions, and unforgettable moments—all in one place for our biggest event of the year. Register now
Join the NetSuite community to innovate, connect, and discover what’s next.
SuiteWorld brings thousands of innovators, builders, and leaders together to learn, connect, and shape what’s next. This October, explore how to build a stronger foundation for growth through inspiring keynotes, major product reveals, hands-on sessions, and unforgettable moments—all in one place for our biggest event of the year. Register now
INVALID_KEY_OR_REF Invalid orderstatus reference key B
I am trying to pre-approve sales orders inside of a before submit hook on create of a sales order. By default, our order status is in the "Pending Approval" ('A') state.
Once I determine that we want the sales order approved, I try to set it the Pending Fulfillment ('B') state.
nlapiSetFieldValue('orderstatus', 'B');
For most of our users, this worked fine. For some, they would get this error:
"INVALID_KEY_OR_REF Invalid orderstatus reference key B" while trying to pre approve a sales order.
I thought it might be a role issue, but I flipped the script to run as administrator, and they still had the same issue. I've also set my role to be the same as theirs, and I can't recreate the issue.
0