Connections for INFACore > Connections to source and target endpoints > Oracle NetSuite

Oracle NetSuite

Create an Oracle NetSuite connection to read from or write to Oracle NetSuite.

Feature snapshot

Operation	Support
Read	Yes
Write	Yes

Before you begin

Before you configure the connection properties, you'll need to get information from your Netsuite account.

The following video shows you how to get information from your Netsuite account:

Connection properties

The following table describes the NetSuite connection properties:

Property	Description
Connection Name	Name of the connection. Each connection name must be unique within the organization. Connection names can contain alphanumeric characters, spaces, and the following special characters: _ . + -, Maximum length is 255 characters.
Username	Applicable only when you use the username and password for authentication. User name for a NetSuite account. User name is an email address.
Password	Applicable only when you use the username and password for authentication. Password for the NetSuite account.
Service URL	NetSuite WSDL URL. From version 2019_2 of the NetSuite WSDL URL, you can enter the WSDL URL used by your NetSuite account instead of the default service URL. The service URL used by the NetSuite account is in the following format: <NetSuite account URL>/wsdl/v2019_2_0/netsuite.wsdl Informatica recommends that you use the WSDL URL that is specific to your NetSuite account. For more information, see Configuring NetSuite account-specific service URL. The default service URL is https://webservices.netsuite.com/wsdl/v2021_2_0/netsuite.wsdl.
Account	NetSuite account ID. To find your account ID, log in to NetSuite, and click Setup > Integration > SOAP Web Services Preferences.
Application ID	Optional. NetSuite application ID. If the application ID property is blank, the agent uses the Informatica application ID. To find your application ID, log in to Netsuite and click Setup > Integration > Manage Integrations. If you do not have an application ID, you can create one. On the Manage Integrations page, click New. After you save the application ID, you can view the application ID number on the Manage Integrations page.
Token ID	Applicable only when you use token-based authentication. The token ID generated in NetSuite.
Token Secret	Applicable only when you use token-based authentication. The token secret generated in NetSuite.
Record Custom Fields	Specify custom NetSuite fields. - Add the custom fields using the following format, where the value of scriptId is the ID field in the NetSuite user interface for each custom field: [<Object Name>] scriptIds = <custom field name1>, <custom field name2>,<custom field name3> For example: [Sales] scriptIds = discountPrice, salesDescription,salesEvent3 - Add the custom fields for NetSuite advanced search using the following format, where the value of scriptId is the ID field in the NetSuite user interface for each custom field: [<Object Name>] scriptIds = <custom field name1>, <custom field name2>,<custom field name3> For example: [EmployeeSearchAdvanced]scriptIds = custentity74,custentity66 - To read or write custom segment data, use the following format to add the custom segment fields: [<Object Name>] custSegScriptIds=custseg1: select,custseg2:multiselect,custseg3:select.... where the value of scriptId is the ID field in the NetSuite user interface for each custom segment field. For example: [Employee] custSegScriptIds=custentity_cseg1: select,custentity_csegcs_multsel:multiselect - To read data from or write data to child record custom segments, use the following format to add the child custom segment fields: [<Object Name>] custSegScriptIds =custseg1:select,custseg2: multiselect,custseg3:select.... For example: [JournalEntry] custSegScriptIds =custbody_cseg1:select,custbody_cseg2:select, custbody_cseg3:select [JournalEntryLineList] custSegScriptIds =custcol_cseg1:select,custcol_cseg2:select, custcol_cseg3:select
Record Filter Fields	Map NetSuite record field names with related NetSuite search record field names so that you can use the fields in filters. List the record field names and related SearchBasic field names, as follows: [<record 1>] <record field name> =<SearchBasic field name><record field name2> =<SearchBasic field name2> [<record 2>] <record field name> =<SearchBasic field name><record field name2> =<SearchBasic field name2><record field name3> =<SearchBasic field name3> For example: [Account] acctName=nameaddr1=address1 To read transactional data from NetSuite when memorized transaction is enabled in the NetSuite account, add the record field names and related SearchBasic field name in the following format: [<record 1>] <record field name> =<SearchBasic field name> For example: [JournalEntry] reversalEntry=memorized
Saved Search Record Fields	Create a separate section for each NetSuite saved search record for which you want to add a saved search field, identified by a unique scriptId. - Add the search fields using the following format: <savedSearchId1>=<savedSearchDeclaredField1Name>, <savedSearchDeclaredField2Name>,<savedSearchCustomFieldScriptId1>, <savedSearchCustomFieldScriptId2>,<StandardJoin>\|<FieldName1>, customSearchJoin\|<scriptID1> For example: 1000=phone,email,custentity78,custentity65, userJoin\|email,customSearchJoin\|custrecord1424 - To read custom segment data, use the following format to add the search custom segment fields: [savedSearchId1]=custseg1:select, custseg2:multiselect, custseg3:select... For example: [741]=custseg1:select,custentity_cseg1:select, custentity_csegcs_multsel:multiselect - To override the metadata of a task, which is created to read custom record standard fields with custom join, use the following format to add the search custom record standard fields: <savedSearchId1>=CustomSearchJoin\| <scriptId of custom record>__<standard field name> For example: 356=CustomSearchJoin\|uss_custom_code__internalId