all of a sudden, with no changes by me we started getting errors that a custom field is read only and cannot be set when upserting customer records.
This was working fine until some time yesterday. Both sandbox and production broke at nearly the same time as far as I can tell, and broke with no user intervention on our part.
The field was indeed disabled (though nothing was in audit log indicating that someone changed it yesterday) and I re-enabled it. Still getting same error.
How is it that API calls can break with NO intervention by anyone in my company and between scheduled netsuite upgrades?
The last time this form was touched was April 5th, and it was working. We have people monitoring daily reports of our API activity. It just broke yesterday out of the blue with the following errors:
[statuscode] => INSUFFICIENT_PERMISSION [statusmessage] => You do not have permissions to set a value for element custentity_lms_companyacctnum 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. [statustype] => ERROR
Pardon my french but WTF? :h_a_w:What changed on Netsuite's side?Second, and sort of related, why have one error message like this, why not have a separate error for :1. permissions2. field is read only3. field is available either when updated or created, but not both.4. feature disabled.which are all VERY different issues.What do Netsuite customers have to pay extra for useful error messages which are explicit and concise?Not to put too fine a point on it but this API and the way Netsuite handles updates to it, ****s. Undocumented unannounced changes are NOT kosher.Every developer on this list should get an email when so much as an i gets dotted or a T crossed in relation to API changes. At the very least a big fat notice should be splashed across support that changes have been made, here are the release notes.This is poor treatment of developers.