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
Custom Field Value Required
When we use webservices to load a job which has custom fields, we do get an error with
<writeResponse>
- <ns2:status isSuccess="false" xmlns:ns2="urn:core_2_6.platform.webservices.netsuite.com">
- <ns2:statusDetail type="ERROR">
<ns2:code>CSTM_FIELD_VALUE_REQD</ns2:code>
<ns2:message>The specified custom field value is missing.</ns2:message>
</ns2:statusDetail>
</ns2:status>
</writeResponse>
This error does not tell you the actual field which is a mandatory field. This is extremely painful to go back and understand which field is causing this error as we have to remove them one by one. Is there a way to figure out the name of the custom field?