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.
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
2 things I'd like for the new year
When adding dynamic fields via addFormField, you have the option of identifying the tab ID. However, this is not an easy thing to derive having to go into the HTML source to find tab IDs.
When you bundle custom records which have custom tabs (or you add custom subtabs in Setup > Customization > Subtabs), they do not keep their assigned IDs when they transfer to the new environment, thus code which adds the dynamic field and tries to assign to one of these tabs needs to be modified to identify the new ID in the new environment.
If you identify a tab ID that is invalid, NetSuite throws an 'unexpected error' instead of gracefully ignoring or throwing a descriptive error for the problem.
0