Rules and guidelines for NetSuite objects in a synchronization task
Consider the following rules and guidelines for NetSuite objects used as sources, targets, and lookups in synchronization tasks:
•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.
•You cannot use advanced data filters for NetSuite sources in synchronization tasks.
•You cannot use parameters defined in a parameter file in data filters for NetSuite sources in synchronization tasks.
•You can remove mapped source fields from a NetSuite source. The synchronization task does not fail as a result.
•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.
•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.
•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<<<<].