Data Integration

supports NetSuite Entity fields, Item fields, CRM fields, Transaction Body/Column/Item fields, and other custom fields. Item Number data is not supported.

NetSuite does not support multiple filters on a field. If you configure multiple filters for a field, the agent uses the last-defined filter for the field.

You cannot perform a NetSuite search on customized fields that reference another record.

Filters for NetSuite Multi-Select and Standard Record custom fields are not supported.

The WSDL version 2014_2 does not include the isBookSpecific column for new book account objects. Consequently, you cannot see the isBookSpecific column with connections that use WSDL version 2014_2.

NetSuite returns both the date and time using the following format for all date or time data types: yyyy-mm-ddThh:mm:ss <AM/PM>. For the TimeOfDay data type, the date defaults to 1970-01-01.

Field metadata information such as primary key or not-null does not display in

Data Integration

.

In an integration template, do not use data type link rules to connect NetSuite sources to source qualifier objects. Use the data type link rule between the source qualifier object and the rest of the data flow.

To use multiple NetSuite sources in a custom integration task, use a NetSuite account that allows concurrent connections.

When you read from

and write to

a NetSuite custom object, ensure that the name of the custom object is not the same as an existing standard object.

When you include custom fields of NetSuite custom objects in a task, they are added to the field list of the child record rather than the parent record. For example, transaction column fields and transaction item options.

Metadata fetch does not work when a saved search record contains custom fields and multi-select standard join fields.

When your NetSuite connection uses SuiteTalk and the BodyOnlyFields parameter is set to false, the Campaign object cannot be read.

Data Integration

does not support NetSuite formula fields.

Due to a NetSuite limitation, if you use a NetSuite connection that uses WSDL 18.1, the task fetches the value of the Language field as ENGLISH_US. The task fetches the value of the Language field as US_ENGLISH if you use a NetSuite connection that uses WSDL 17.2 or earlier version.

When you use a Netsuite connection, which contains saved search record fields in Connection attribute, to create a task to read from NetSuite saved search, the agent appends

_CSJ

to custom fields. Also, when you edit or refresh an existing task that reads from NetSuite saved search, the agent appends

_CSJ

to custom fields.

If you edit or refresh an existing task to read from a saved search object that has an internalid or externalid field, the task might fail with the following error message:

Transformation stopped due to a fatal error in
the mapping. The expression [internalId_InternalId] contains the
following errors [<<PM Parse Error>>
[internalId_InternalId]: invalid symbol reference ... >>>>internalId_InternalId<<<<].