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.
Expand your NetSuite knowledge by joining our Ask A Guru Live sessions. RSVP on this event now.
Nominate Your Peers for NetSuite Support Community's Choice of the Quarter! Submit your nomination today.
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. Explore new breakthroughs, sharpen your skills, and connect with experts who are shaping what’s next. Experience bold keynotes, interactive learning, and connections that span the global NetSuite community. Discover what's next at SuiteConnect Tour 2026.
NetSuite launches new wholesale distributions solution in Japan in January 2026!

NetSuite has launched SuiteSuccess Wholesale Distribution Edition, in Japan. Please join us the webinar on February 12 that introduces NetSuite solution with demos and case studies for Wholesale Industry.

Register Now
NetSuite 2026.1 Release Notes - This document summarizes the changes to NetSuite between 2026.1 and the previous release.

Have questions or experiences to share? Post your Release 2026.1 questions and join discussions in the Release 2026.1 category.

Remove (#) From Custom Segment Transaction Fields After Bundle Installation

edited Jan 23, 2026 9:20PM in Ask A Guru 4 comments

Hi!

We recently built some extensive workflow updates in Sandbox. Carefully tested everything, and then used a bundle to move them over to Prod. We have two custom segments, one of which is a heavy dependency in the workflows. When I installed the bundle, it changed the names of the custom segment transaction column field by appending (4) to it. The header field name remains unchanged.

Now, I've seen this behavior before with custom fields, when the field is part of the bundle but already exists in Production. The fix is easy; let it duplicate the fields, and then remove the duplicate or rename the field to remove the additional suffix. Check all references, etc. But I cannot find anywhere to update the name of the transaction line level custom segment reference. I've checked transaction line and body fields, the custom segment custom record, the custom segment configuration. Nothing.

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