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.
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!
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.
Nominate Your Peers for NetSuite Support Community's Choice of the Quarter! Submit your nomination today.
Intelligent Payment Automation version 1.0.3 is now available in the SuiteApp Marketplace. The SuiteApp, powered by BILL, lets you automate payments, manage vendor details, and bank account information within NetSuite. Learn more

"When a record is created or updated, but not in both cases"

edited Jun 5, 2020 6:25PM in SuiteCloud / Customization 2 comments

I imagine that everyone has seen a permissions error before:
[INDENT]You do not have permissions to set a value for element custentitypi_url due to one of the following reasons: 1) The field is read-only; 2) An associated feature is disabled; 3) The field is available either when a record is created or updated, but not in both cases.[/INDENT]

Could someone tell me how I can tell if condition "3" is true? I'm fairly certain 1 and 2 are false.

I'm trying to set a custom field on a contact, and I don't see anything in the Netsuite customization interface that specifies if a field should be settable on create vs update. I'm using the SOAP API, and have successfully set a custom field in one Netsuite account, but am seeing this error in a second account (that had some customization done by a third party during implementation). My best guess is that the forms or entities are misconfigured somehow.

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 4 (Oct-Dec 2025)

This Week's Leaders

This Month's Leaders

All Time Leaders