Rules and Guidelines for NetSuite Objects
Consider the following rules and guidelines for NetSuite objects used as sources, targets, and lookups in mappings and mapping configuration tasks:
- •Informatica Cloud 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, Informatica Cloud 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 Informatica Cloud.
- •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.