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
2017.2 require
Just pointing this out for everyone here in this group.
2017.2 script changes that might affect your current code.
Keep in mind that configuration of a require Object is optional. If you must configure a require Object,
the @NAmdConfig tag is suited for general use. In limited cases, such as when you need run-time
control over configuration options, use the require.config() method.
As of 2017.2, you must update your existing scripts that call require Configuration. Scripts that use
runtime calls of require Configuration throw an INVALID_AMD_CONFIG_PATH__1 error when:
■ The call does not include the context property.
■ The call includes the context property but its value is a path that conflicts with other entry point
0