My Stuff
Comments
-
Hi, After further investigation, it turned out that the user had a custom form set as the "preferred" form for customers, with terms and credit limit disabled (i.e. read only), e.g: The issue was fixed by setting the default customer form as the preferred form for the API integration's role, overriding the company default.…
-
Hi Richard, While setting ignoreReadOnlyFields to true generates a successful response, it does not actually update the credit terms for the customer. So it seems that terms is read-only for SOAP on the affected instances of NetSuite. What could cause it to be read-only for SOAP? I can confirm that terms can be modified…
-
Hi @Richard James Uri-Oracle, Here's a request that replicates the issue, with the TokenPassport removed but with the remainder of the header intact: <soap-env:Envelope xmlns:soap-env="http://schemas.xmlsoap.org/soap/envelope/"> <soap-env:Header> <ns0:searchPreferences…