Property | Description |
|---|---|
Runtime Environment | The name of the runtime environment where you want to run the tasks. |
Token ID | The token ID generated in NetSuite. Required if you want to use token-based authentication to access NetSuite. Optional if you use a user name and password to access NetSuite. |
Token Secret | The token secret generated in NetSuite. Required if you want to use token-based authentication to access NetSuite. Optional if you use a user name and password to access NetSuite. |
Username | User name for a NetSuite account. User name is an email address. Optional if you use token-based authentication to access NetSuite. |
Password | Password for the NetSuite account. Optional if you use token-based authentication to access NetSuite. |
Service URL | NetSuite WSDL URL. If your NetSuite account does not use the default NetSuite WSDL URL, enter the WSDL URL used by your NetSuite account. |
Account | NetSuite account ID. To find your account ID, log in to NetSuite and click Setup > Integration > Web Services Preferences. If you cannot access the Setup menu, navigate to Support > Go to Suite Answers > Contact support by phone. The page will display your account ID. |
Application ID | NetSuite application ID. Required when you use WSDL URL version 2015_2 or above without token-based authentication. 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. |
Record Custom Fields | Specify custom NetSuite fields so that they are available in Informatica Cloud. 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 If you want 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 If you want 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 | Saved search fields in NetSuite do not appear in Informatica Cloud if they have a null value, by default. Add saved search fields to ensure that saved search fields are available in Informatica Cloud even when they have a null value. 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 If you want 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 If you want 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 |