The administrator can perform the following tasks to ensure that NetSuite fields are available in
Data Integration
and to optimize performance:
If field names in the NetSuite record and the related NetSuite search record do not match, the fields cannot be used in filters. This must be configured before NetSuite objects can be used as sources in tasks.
You can associate NetSuite record field names with related NetSuite search record field names when you set up a NetSuite connection in
Data Integration
. Alternatively, you can configure the
RecordToFieldsMap.ini
file if the connection uses a Secure Agent group for the runtime environment.
Some custom fields in NetSuite custom objects might not appear in
Data Integration
, particularly transaction body fields and transaction column fields.
To ensure that all custom fields are available in
Data Integration
, you can configure custom fields when you set up a NetSuite connection in
Data Integration
. Alternatively, you can configure the
NetSuiteCustomFields.ini
file if the connection uses a Secure Agent group for the runtime environment.
Saved search fields in NetSuite do not appear in
Data Integration
if they have a null value.
You can specify saved search fields when you configure a NetSuite connection so that the saved search fields appear in
Data Integration
even when they have a null value. Alternatively, you can add the saved search fields to the
NetSuiteSavedSearchFields.ini
file if the connection uses a Secure Agent group for the runtime environment.