Discussions
Join us for complimentary one-day events around the world and step into a future fueled by AI and limitless potential. Explore new breakthroughs, sharpen your skills, and connect with experts who are shaping what’s next. Experience bold keynotes, interactive learning, and connections that span the global NetSuite community. Discover what's next at SuiteConnect Tour 2026.
We’re excited to announce that the 2025 Community Recap is now available! This special recap highlights the amazing contributions and achievements of our members over the year and celebrates the collective success of our community.
Check your personalized recap to see the impact you made in 2025 and how your efforts helped shape our community’s growth and success.
View Your 2025 Community Recap
Thank you to everyone for your passion, collaboration, and support. Here’s to building an even stronger community together in the year ahead!
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