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.
SuiteWorld | October 25–28, 2026 | Las Vegas Where our community gets ready for 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. Join us
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. Join us
Error in custom forms trying to save (custom field exists)
I know this was an issue some time ago, but appears to be again.
I have a custom record which I can setup a new form, move or change field display types, and save without issue. However when I go back and edit the form (even if I don't do a thing), when I save, it gives me the error "This custom field already exists".
I do not have field groups, I have not moved fields around, I do not have redundant labels, nothing. This is pretty plain vanilla form. If I delete the form, create a new one, do what I want to do on the form and save it, it saves without issue. Go back and edit it and try and save and up pops the error again.
0