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!
Stay in the Know
Be sure you're subscribed to NetSuite communication to stay in the know about monthly happenings, updates and announcements. Subscribe
Be sure you're subscribed to NetSuite communication to stay in the know about monthly happenings, updates and announcements. Subscribe
Please note that on Friday, March 20, 2026, at 8:00 PM Pacific time, our Case Management System will undergo a scheduled maintenance for approximately 4 hours. During this time, case creation via SuiteAnswers will be unavailable and inbound calls will be routed to Customer Service.
Can't add sales order via php
Hello Everyone,
I have been trying to create a sales order using the php 2010.1 toolkit but for some reason it says I do not have the correct permissions. I am a sales administrator and I can create them manually from netsuite.com without any issues. I have specified the correct role in the login credential file.
Error from order.php
[code]
['code'] => INSUFFICIENT_PERMISSION
['message'] => You do not have permissions to set a value for element entity 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.
I have been trying to create a sales order using the php 2010.1 toolkit but for some reason it says I do not have the correct permissions. I am a sales administrator and I can create them manually from netsuite.com without any issues. I have specified the correct role in the login credential file.
Error from order.php
[code]
['code'] => INSUFFICIENT_PERMISSION
['message'] => You do not have permissions to set a value for element entity 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.
0