TABLE API is not updating the read-only fieldsThis behavior is expected. The Table API enforces the same restrictions as the platform's user interface (UI). Specifically, it ensures that read-only fields cannot be modified through standard API interactions, just as they cannot be altered directly within the UI. When a user attempts to modify a record that includes read-only fields via the Table API, the API call will behave in a manner similar to the UI. The inbound API request will be processed successfully, and the system will return a 200 status code, indicating that the request was handled correctly. However, the read-only fields will remain unchanged, as the API respects the same restrictions applied to them within the UI. To modify read-only fields through the API, an alternative approach is required. This can be achieved by utilizing a Scripted REST API, which allows the execution of custom scripts. In this case, the script runs explicitly and can bypass the restrictions on read-only fields (just like way we run background/server side scripts), enabling updates to be made as desired. Note: Disabling "Override Read Only" on the field will help in modifying the value using REST and SOAP