megaphone
Update your Profile with your Support type to get your Support Type badge.
Nominate Your Peers for NetSuite Support Community's Choice of the Quarter! Submit your nomination today.
Expand your NetSuite knowledge by joining our Ask A Guru Live sessions. RSVP on this event now.
Now is the time to ask your NetSuite-savvy friends and colleagues to join the NetSuite Support Community! Refer now! Click here!
What Topic Should We Cover Next? Your idea could be our next feature—drop your suggestion now!
No Limits. Just possibilities. Join us for complimentary one-day events around the world and step into a future fueled by AI and limitless potential. Discover what's next at SuiteConnect Tour 2026.
Try Intelligent Payment Automation – Fee Free For Your First Month For more information, visit this thread.

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.
Now is the time to ask your NetSuite-savvy friends and colleagues to join the NetSuite Support Community! Refer now! Click here to watch and learn more!

Replacing jQuery UI

edited Dec 2, 2019 5:44PM in SuiteCloud / Customization 4 comments

Probably like others, we have a script that used jQuery UI. While that has not been officially supported in the past, it also was not officially blocked. Our scripts used jQuery to add script resources to the page like so:

 var resources = [                'https://ajax.googleapis.com/ajax/libs/jqueryui/1.11.4/jquery-ui.min.js'       ];    for (var i = 0, count = resources.length ; i < count ; i++) {       jQuery("head").append("<script type='text/javascript' src='"+resources[i]+"' /></script>");  } 


That allowed us to import libraries needed in the script that weren't already included. Now that jQuery UI is not included by NetSuite it must be imported independently. The method has been working fine for years but now seems to have no effect. This of course causes subsequent calls to fail and that's how I discovered it. Is this no longer possible? Did the 2017.1 release notes leave that out?

Howdy, Stranger!

Log In

To view full details, sign in.

Register

Don't have an account? Click here to get started!

Leaderboard

Community Whiz

Quarter 1 (Jan-Mar 2026)

This Week's Leaders

This Month's Leaders

All Time Leaders