Hello, I'm following the Netsuite documentation to update the createddate field via REST API V1 (https://system.netsuite.com/help/helpcenter/en_US/APIs/REST_API_Browser/record/v1/2024.2/index.html#) for some Sales Orders. I have configured postman correctly, sending this request in the body: { ‘createdDate": ’2024-10-01T131123.000Z’ } My header is: https://{{AccountID}}.suitetalk.api.netsuite.com/services/rest/record/v1/salesOrder/4457 Note: I hide my AccountID for security In response, I receive the message 204 - No content and the following detail X-Content-Type-Options: nosniff Pragma: No-Cache: Cache-Control: No-Cache Expires: 0 Location: https://{AccountID }.suitetalk.api.netsuite.com/services/rest/record/v1/salesorder/4457 Vary: User-Agent Date: Tue, 18 Feb 2025 183133 GMT Connection: keep-alive Akamai-GRN: 0.9a9c7a5c.1739903433.341d4d68 Transaction SO 4457 has the following status: ‘Pending Fulfillment’. I have validated with ChatGPT and it indicates the following: ‘In the technical description (Record Browser) NetSuite lists createdDate as a date-time type field, suggesting that it ‘could’ be updated. However, in practice, NetSuite applies audit controls and does not allow retroactive changes to the creation date when the transaction already has accounting movements (invoicing, fulfilment, etc.)’. However, the status of the transaction ‘Pending Fulfillment’ is open. Can anyone help me. Thanks!

AI generated answer (using internal Slack threads):

Based on the conversations provided, it seems that the issue you're facing is related to NetSuite's audit controls. Even though the

createdDate

field is listed as a date-time type field that could be updated, NetSuite does not allow retroactive changes to the creation date when the transaction already has accounting movements (invoicing, fulfillment, etc.). Even though the status of the transaction is 'Pending Fulfillment', which is considered open, it seems that NetSuite still applies these audit controls. Unfortunately, there doesn't seem to be a workaround for this issue based on the information provided in the conversations. ****** Disclaimer: This response was generated by an artificial intelligence assistant based on previous conversations from multiple Slack channels, and may contain inaccuracies or mistakes. ******