NetSuite Support Limitations and Known Issues

Here are some things to keep in mind when using creating layouts for NetSuite records.

Limitations

These NetSuite features are not supported by the add-in:

• Record actions
• Transforming records
• Upsert operation

These add-in features are not currently available for integrated workbooks connected to NetSuite services:

• Send only changed data

Known Issues

Feature Area	Issue	Description
Mandatory Properties	The add-in cannot properly set default values for the "Required for Update" and the "Required for Create" properties for a field.	The OA3 service metadata document does not provide the "Required" property for schema members (fields). You can manually configure these properties using the Business Object Field Editor. See Configure Business Object Fields.
Data Download	Download performance is suboptimal.	A separate GET request is needed for each row because there is no way to get all fields for several rows in a single GET request. This limitation causes performance to suffer.
	The GET request for a single item does not include some of the expected fields in the response payload.	For example, "Last Sale Date" and "Opening Balance" in a "customer" business object.
	Query by Internal ID field returns an error
Data Upload	Some fields in some NetSuite services do not accept a null value in a POST/PATCH request even though the service metadata document describes them as "nullable".	Workaround: Review the error message details to identify the fields causing the error, then configure these fields to omit empty values from the payload. See Omit Empty Values During Upload.
	After a successful upload to add or update a row, the row's values in the layout does not reflect changes made on the server.	In this case, the response does not include the updated fields. The user will need to re-download to see any changes.
	When uploading Create/Update rows, the error message returned by the service is missing specific details.	You instead see a generic message such as "Error while accessing a resource. Field must contain a value." is returned without indicating which field it is.
	Conflict detection is not supported	If a user uploads changes to the service that overwrite another user's recent changes, the upload succeeds with no notification of the conflict.
Lists of Values	List of values are not configured automatically on business object fields.	Configure fields with list of values using a local data source. See Create a Local Data Source for a List of Values and Configure a List of Values with a Local Data Source.