Hi, I'm Ask INFA!
What would you like to know?
ASK INFAPreview
Please to access Ask INFA.
Communities
A collaborative platform to connect and grow with like-minded Informaticans across the globe
Product Communities
Connect and collaborate with Informatica experts and champions
Discussions
Have a question? Start a Discussion and get immediate answers you are looking for
User Groups
Customer-organized groups that meet online and in-person. Join today to network, share ideas, and get tips on how to get the most out of Informatica
Get Started
Community Guidelines
Knowledge Center
Troubleshooting documents, product guides, how to videos, best practices, and more
Knowledge Base
One-stop self-service portal for solutions, FAQs, Whitepapers, How Tos, Videos, and more
Support TV
Video channel for step-by-step instructions to use our products, best practices, troubleshooting tips, and much more
Documentation
Information library of the latest product documents
Velocity (Best Practices)
Best practices and use cases from the Implementation team
Learn
Rich resources to help you leverage full capabilities of our products
Trainings
Role-based training programs for the best ROI
Certifications
Get certified on Informatica products. Free, Foundation, or Professional
Product Learning Paths
Free and unlimited modules based on your expertise level and journey
Resources
Library of content to help you leverage the best of Informatica products
Tech Tuesdays Webinars
Most popular webinars on product architecture, best practices, and more
Product Availability Matrix
Product Availability Matrix statements of Informatica products
SupportFlash
Monthly support newsletter
Support Documents
Informatica Support Guide and Statements, Quick Start Guides, and Cloud Product Description Schedule
Product Lifecycle
End of Life statements of Informatica products
Ideas
Events
Change Request Tracking
Marketplace
English
  • Data Integration Connectors
  • All Products

Table of Contents

Search

  1. Introduction to NetSuite Connector
  2. Connections for NetSuite
  3. Synchronization tasks with NetSuite
  4. Mappings and mapping tasks with NetSuite
  5. Appendix A: NetSuite data type reference

NetSuite Connector

NetSuite Connector

Back Next

Configuring the NetSuiteSavedSearchFields.ini file

Configuring the NetSuiteSavedSearchFields.ini file

You can specify saved search fields in the
Saved Search Record Fields
 connection property when you configure a NetSuite connection to ensure that all saved search fields are available in
Data Integration
. Alternatively, if the NetSuite connection uses a Secure Agent group as the runtime environment, you can configure the
NetSuiteSavedSearchFields.ini
 file.
If you choose to configure the
NetSuiteSavedSearchFields.ini
 file, perform the following steps:
  1. Make a copy of the
    NetSuiteSavedSearchFields.ini
     file, located in the following directory:
    <Secure Agent installation directory>\downloads\packageNetsuiteConnector.<version>\package\rdtm\javalib
  2. Use the following guidelines to change the file to include all of the saved search 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: 
      [SavedSearchScriptIdToFieldsMap<version>]
<savedSearchId1>=<savedSearchDeclaredField1Name>,<savedSearchDeclaredField2Name>,
<savedSearchCustomFieldScriptId1>,<savedSearchCustomFieldScriptId2>,<StandardJoin>|<FieldName1>,
customSearchJoin|<scriptID1>
      The savedSearchId1 is ID field in the NetSuite user interface that specify the saved search record. The savedSearchDeclaredField1Name and savedSearchDeclaredField2Name are standard field names in the NetSuite user interface. The savedSearchCustomFieldScriptId1 and savedSearchCustomFieldScriptId2 are ID fields in the NetSuite user interface for custom fields. The StandardJoin|FieldName1 is the standard join field and customSearchJoin|scriptID1 is the custom join field.
      For example: 
      [SavedSearchScriptIdToFieldsMap1]
1000=phone,email,custentity78,custentity65,userJoin|email,customSearchJoin|custrecord1424
      In the example, 1000 is the saved Search ID, phone and email are standard field names, custentity78 and custentity65 are the script IDs of a custom field. userJoin|email is the standard join field and customSearchJoin|custrecord1424 is the custom join field script ID.
      When you use custom join, script ID appears in the
      Data Integration
       user interface.
    • If you want to read custom segment data, use the following format to add the search custom segment fields: 
      [SavedSearchScriptIdToCustSegFieldsMap]
savedSearchId1 = custseg1:select,custseg2:multiselect,custseg3:select....
      where custom segment field scriptId is appended to field type (select or multiselect) with ":" delimiter.
      For example: 
      [SavedSearchScriptIdToCustSegFieldsMap]
741=custseg1:select,custentity_cseg1:select,custentity_csegcs_multsel:multiselect
  3. Save the
    NetSuiteSavedSearchFields.ini
     in the following location:
    <Secure Agent installation directory>\apps\Data_Integration_Server\ext\deploy_to_main\bin\rdtm-extra\reserved\userfiles\netsuite
0 COMMENTS
We’d like to hear from you!