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!
Update your Profile with your Support type to get your Support Type badge.
Don't miss out on our Question of the Week! You only have until tomorrow, October 23, 2025, 2PM ET to comment your answers and earn rewards! Click here for more details.
Uncover the power of data with the Analytics Hub —your ultimate guide to mastering NetSuite Saved Searches and Reports. Simplify the complex and unlock your organization's true potential. Dive into the Analytics Hub now and soar to new heights!
To help you get the most out of your 2025.2 Release Preview account, review the topics outlined in the 2025.2 Release Preview Guide.
Nominate Your Peers for NetSuite Support Community's Choice of the Quarter! Submit your nomination today.
Intelligent Payment Automation version 1.0.3 is now available in the SuiteApp Marketplace. The SuiteApp, powered by BILL, lets you automate payments, manage vendor details, and bank account information within NetSuite. Learn more

Bug in Custom Buttons in 2013.2

edited Dec 3, 2019 2:47PM in General 2 comments

So I've got a weird issue happening. We've got a set of 4 custom buttons on our Sales Orders that are scripted to do different things (make a special PDF, run a related search, etc). The top copy of the 4 buttons all work correctly. In the bottom set of buttons, two of my 4 buttons are causing the same action to fire. As far as I knew, the top buttons and bottom buttons are supposed to be exact duplicates. I certainly haven't programmed them in separately.

I have no idea what to do about this, except to tell people to use the top set only for the time being. Does anyone know what this could be? I'm believing that it's related to 2013.2 since it just cropped up, but it could have been doing this prior to our upgrade and just went unnoticed. It's doing the same thing in different browsers, users, records, etc., so it's not a caching issue of some kind.

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 4 (Oct-Dec 2025)

This Week's Leaders

This Month's Leaders

All Time Leaders