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
Client side scripts requiring users to clear cache?
For the past month or so, we have noticed that when we update Client side scripts, the new versions only take effect if the users clear their browser cache. This is odd as before, a simple refresh, or at worst a CTRL-F5 would do the job. It's also odd as technically, this doesn't seem like a Netsuite problem, since it's client-side code, but then again it only started to be a problem recently, and it seems to be a problem on all accounts we deploy on.
Anyone else notice this problems? Could it be somehow a NS problem, maybe in the way NS attaches scripts to forms, causing browsers not to detect the change?
0