Limitations of REST Web Services
Keep the following in mind when working with REST web services.
-
Queries only return record IDs and HATEOAS links. (See HATEOAS.) That is, query results have a form of non-expanded references. Also, you can only use body fields in query conditions.
-
Translations in REST web services work the same way as in SuiteScript. For custom records, a user’s language preference (Home > Set Preferences > Language) is taken into account. For standard records, translations are returned and updated in the company’s primary language. Additionally, in the current version of REST web services, it is not possible to read and update translations on the translation sublist for both custom records and standard records. This behavior is different from the behavior of SuiteScript.
-
REST web services don't support legacy tax features. To work with taxation through REST web services, you must have the SuiteTax feature enabled. For more information about using SuiteTax, see SuiteTax.
-
Asynchronous request execution isn't supported in the REST query service.
-
REST web services always load record instances in edit mode, even for GET requests. When a user without the Administrator role tries to run a GET request for an employee record of a user with the Administrator role, this error message will appear: “For security reasons, only an administrator is allowed to edit an administrator record”. This prevents users without the Administrator role from editing the employee record of a user with the Administrator role.
To save \n and \r strings through REST you need to escape the strings into \\n and \\r.
-
Custom sublists are not available in REST web services.