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!
Update your Profile with your Support type to get your Support Type badge.
Expand your NetSuite knowledge by joining our Ask A Guru Live sessions. RSVP on this event now.
Don't miss out on our Question of the Week! You only have until tomorrow, September 11, 2025, 2PM ET to comment your answers and earn rewards! Click here for more details.
Uncover the power of data with the Analytics Hub —your ultimate guide to mastering NetSuite Saved Searches and Reports. Simplify the complex and unlock your organization's true potential. Dive into the Analytics Hub now and soar to new heights!
NetSuite 2025.2 Release Notes - This document summarizes the changes to NetSuite between 2025.2 and the previous release.
To help you get the most out of your 2025.2 Release Preview account, review the topics outlined in the 2025.2 Release Preview Guide.
SuiteWorld October 6 - 9, 2025: Agenda Builder is live!

Read on for the latest updates including:
• Agenda Builder launch
• SuiteWorld On Air registration
• New NetSuite Prompt Studio Contest
• And more!

Check out this thread to learn more!

"Invalid Field Value" error for custom field of type integer number

edited Dec 2, 2019 4:35PM in SuiteCloud / Customization 5 comments

Hello,

I am having an issue where I am trying to set a custom field value of type integer number on new record using the N/record.record's setCurrentSublistValue. This is usually extremely straight forward. The value is initially read as a string so when it is time to set the value, it is of type string. I've tried Number(<value>), String(<value>) and parseInt(<value>) and all of the return the same error of :

"You have entered an Invalid Field Value <value> for the following field: <custom field id>" which for example if it the value i am trying to set is 36, it is trying to set this as 36.0 whether string or number. Has anyone ran into this? This is the ONLY field that is causing this type of issue. I know that for the most part, fields are happy with string values but this one is causing me problems :h_a_w:

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 3 (Jul-Sep 2025)

This Week's Leaders

This Month's Leaders

All Time Leaders