Rules and Guidelines for NetSuite V2 Objects
Consider the following rules and guidelines for NetSuite V2 objects used as sources in Data Synchronization tasks, mappings, and Mapping Configuration tasks:
- •You cannot perform a NetSuite search on customized fields that reference another record.
- •You cannot use parameters defined in a parameter file in data filters for NetSuite sources in Data Synchronization tasks.
- •Field metadata information such as primary key or not-null does not display in Informatica Cloud.
- •Select or Multi-Select type fields drill down to two types: <field name>_value and <field name>_text.
- •You can configure filters only for Search Standard Records.
- •The first time metadata fetch takes a longer time. The issue does not exist for subsequent runs.
- •NetSuite does not support reading the user note object as a child object. If you create a task with the user note object as a child object, for example, contact_child_usernote, the task fails with an error.
Consider the following rules and guidelines for NetSuite V2 objects used as targets in Data Synchronization tasks, mappings, and Mapping Configuration tasks:
- •When you use a single parent object in a mapping, you must map the externalid field for update, upsert, and delete operations. You must also add the externalid field as an update column field.
- •When you use a single parent object in a data synchronization task, you must map the externalid field for update, upsert, and delete operations.
- •When you use a multi child object in a data synchronization task, you must map the parent externalid for all the operations. When you use a child object, map the linenumber field of the child object for update, upsert, and delete operations.
- •When you use a multi child object in a mapping, you must map the parent external id for all the operations. When you use a child object, use the update field property to define the key. Map the field in the field mapping for update, upsert, and delete operations. If you map the linenumber field, the task fails with an error.
- •If the externalid field is mapped, by default, it is used as the update column field. To use a different update column field, you must unmap the external id field and then select a different update column field.
- •For Multi-Select fields, the format should be ["String1","String2"] or [String1,String2] or String1,String2.