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
"Invalid custom field record type"
I'm trying to do a CSV update for a new custom field I've created for the Customer record. This is setup as an Integer Number type of field, and my csv is simply the Internal ID and a number field. What is strange is that of the 365 Customer accounts that I am trying to update, 46 of them DID update while the rest did not. Does anyone have any idea on why my csv update would fail when I can simply go into the UI and update the field without any issue?
I previously had the same thing happen when I added new custom fields and tried to update them. I tried several truly random things to fix it and it seems to have fixed itself in the end. It doesn't seem possible that the error is actually related to the specific field I'm trying to update, and I've started to wonder if this isn't actually an issue with other fields on the record. We do currently have a large number of fields so perhaps the record is simply too cluttered? I would appreciate any assistance as I don't relish the prospect