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 $300 - 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
NSC | ORA-02290 Check Constraint (NLCOMPANY.INVTITEMSERIALCMCHECK) Violated on Saving
On issue 575649 Workflow > Serialized Inventory Item > Set Field Value Applied on Costing Method Field > Error: ORA-02290 check constraint (NLCOMPANY.INVTITEMSERIALCMCHECK) violated on Saving, it was mentioned that the error, ORA-02290 Check Constraint (NLCOMPANY.INVTITEMSERIALCMCHECK) Violated on Saving, will show if there is a Workflow running on the Item record that has the action Set Field Value on the Costing Method field that set "Specific" values.
It is possible to resolve by doing the following:
○ Looking under Purchasing/Inventory tab in the Item record, the Costing Method field has two "Specific" values on the list
○ The workflow creates a duplicate "Specific" option having the value of "SERIAL"
0