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
Problem importing to custom transaction body field via CSV import
I've actually figured this out, but as I couldn't find an answer online, I'm posting anyway in case someone else has the same problem, which seems fairly likely as there's no warning or message from NetSuite about the issue and it doesn't cause an error as such.
I was trying to update a list/record type custom field we have that stores a reference to another transaction, e.g., "Invoice #<document number>", but although the import was saying it was completed, nothing was happening to the field and it remained empty.
It turned out that the mapping was matching the field name "FOC's Original Order" because it matched on the import file, but it was unable to process the input because of the apostrophe in the name. It was necessary to remove it from the file and manually map it instead.