Mapping NetSuite Custom Segment to SuiteProjects Pro Dropdown Using Advanced Mapping

SuiteProjects Pro supports standard list or multi-select custom segment fields from NetSuite when using the SuiteProjects Pro NetSuite integration. However, if you try to directly map a dropdown-type custom field from NetSuite into SuiteProjects Pro, no value will be passed during synchronization.

This occurs because SuiteProjects Pro requires conditional logic (using IF/END) for dropdown mappings when referencing internal IDs from NetSuite custom segment fields.

Incorrect Implementation (Does Not Work)

Attempting to map the values directly using an XML-style tag does not pass values correctly:

<oa_custom_dropdown custentity_cseg_ns_custom_segment_list>

  ‘Dropdown item 1’ ‘1’

</oa_custom_dropdown>

In this example, ‘1’ is the internal ID of the NetSuite segment value, and ‘Dropdown item 1’ is the corresponding label expected in SuiteProjects Pro. However, this mapping is ignored.

Correct Implementation (Using Conditional Logic)

Instead, use an IF statement to map based on the internal ID value. This is the correct way:

IF <<END

  IF (custentity_cseg_ns_custom_segment_list = ‘1’) THEN oa_custom_dropdown ‘Dropdown item 1’

END

This explicitly checks the internal ID of the NetSuite field and maps it to the correct dropdown option in SuiteProjects Pro.

Best Practices

• Always reference internal IDs, not display values, from NetSuite.
• Use one IF statement for each possible dropdown value.
• Ensure the value in oa_custom_dropdown matches exactly what SuiteProjects Pro expects.