megaphone
Update your Profile with your Support type to get your Support Type badge.
Nominate Your Peers for NetSuite Support Community's Choice of the Quarter! Submit your nomination today.
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, March 12, 2026, 2:00PM ET to comment your answers.
Now is the time to ask your NetSuite-savvy friends and colleagues to join the NetSuite Support Community! Refer now! Click here!
What Topic Should We Cover Next? Your idea could be our next feature—drop your suggestion now!
No Limits. Just possibilities. Join us for complimentary one-day events around the world and step into a future fueled by AI and limitless potential. Discover what's next at SuiteConnect Tour 2026.
Try Intelligent Payment Automation – Fee Free For Your First Month For more information, visit this thread.

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!

"Invalid custom field record type"

edited Dec 3, 2019 2:42PM in General 2 comments

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

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 1 (Jan-Mar 2026)

This Week's Leaders

This Month's Leaders

All Time Leaders