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!

NetSuite 2025.2 Release Notes - This document summarizes the changes to NetSuite between 2025.2 and the previous release.

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.

SuiteWorld October 6 - 9, 2025: Agenda Builder is live!

Read on for the latest updates including:
• Agenda Builder launch
• SuiteWorld On Air registration
• New NetSuite Prompt Studio Contest
• And more!

Check out this thread to learn more!

NSC | Impacts of Changing Custom Field IDs to Customizations that reference them

Jun 1, 2022 2:42AM edited Apr 25, 2023 8:59PM in SuiteCloud / Customization

Scripts, Workflows, and other Customizations may reference Custom Fields by their Field IDs. See screenshots below:

Changing the Field IDs may cause the customizations to not work. So, it is best practice to set Custom Field IDs during their creation to a meaningful value that clearly identifies the field or its purpose. For example, the Field ID for the Custom Field above should have been set to an identifier such as custbody_workinstruction.

Let us know what you think about this topic by leaving a comment or using the reaction buttons below.

-Jack