megaphone
Update your Profile with your Support type to get your Support Type badge.
Nominate Your Peers for NetSuite Support Community's Choice of the Quarter! Submit your nomination today.
Stay in the know of how NetSuite can help grow your business with our guides, webinars, and events. Subscribe Here
What Topic Should We Cover Next? Your idea could be our next feature—drop your suggestion now!
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. Discover what's next at SuiteConnect Tour 2026.
Try Intelligent Payment Automation – Fee Free For Your First Month For more information, visit this thread.
New AI Community Guidelines. Please review and follow them to ensure AI use stays safe, accurate, and compliant.
Expand your NetSuite knowledge by joining our Ask A Guru Live sessions. RSVP on this event now.
Don't miss out on our Pop Quiz! You only have until tomorrow, April 3, 2026, 11:00AM ET to comment your answers.

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!
New AI Community Guidelines. Please review and follow them to ensure AI use stays safe, accurate, and compliant.
Stay in the Know

Be sure you're subscribed to NetSuite communication to stay in the know about monthly happenings, updates and announcements. Subscribe

specific field Id crashes UI search

edited Jan 3, 2020 1:24AM in Search / Reporting 1 comment

I have a custom record with a field id of: custrecord_claim_isinuse that when used in a search will crash (UNEXPECTED_ERROR)

Your Customer Care Case # is 766317



If I rename it to: custrecord_claim_isinuse2 it won't crash.

What is wrong with "custrecord_claim_isinuse"?  I've spent HOURS chasing this down.  The bug was first noticed in SuiteScript, that took a long time to find... removing column one by one.  Then back to the UI to test it there.

Then another bug with custom records, field Ids and searches.  To get the field Id to REALLY commit you need to:[LIST=1]

Steve Klett | Senior Developer
NetValue Technology

image-8cb77df5036e1-7e7f.png

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