Discussions
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.
We’re excited to announce that the 2025 Community Recap is now available! This special recap highlights the amazing contributions and achievements of our members over the year and celebrates the collective success of our community.
Check your personalized recap to see the impact you made in 2025 and how your efforts helped shape our community’s growth and success.
View Your 2025 Community Recap
Thank you to everyone for your passion, collaboration, and support. Here’s to building an even stronger community together in the year ahead!
Season’s greetings to you and yours! As we head into the holidays (December 24 – January 4), we want to take a moment to celebrate the incredible strength and collaboration within our community. Even during the break, you can continue to benefit from connecting with peers, searching related threads, posting your questions, and marking helpful replies as “Accepted” in the Support Community.
Please note our dedicated team will be on reduced coverage during this time, and regular responsiveness will resume on January 5. Wishing you a joyful and restful holiday season!
-The NetSuite Support Community Team
Bug? Changing hidden list/record column field to disabled via script
I have a requirement where normally an item column field on transactions would be completely hidden and not used, unless the user matches a specific criteria.
So I set up three column fields:
1. a list/record type and sourced to a list/record field on the item record.
2. the other two are date column types sourced to date fields on the item record.
I set all of these to 'hidden' by default. Then in a user event beforeload script, I check for the user criteria and if valid, I set these three columns to be visible. I know that you need to always first set these fields to 'normal' display when bringing a normally hidden field visible so I do this first. Then I set the three fields to disabled (so they are inline displayed).