Dynamic Default Value Sourcing for Custom Segments

In some cases, you can apply a custom segment to two record types that have a relationship with each other. In these situations, you may want the segment value on one record to populate with the value selected on the other.

For example, in the standard NetSuite configuration, each sales transaction is associated with a particular customer record. You may want the segment value on a new sales transaction to populate with the segment value saved on the corresponding customer record. You can configure this behavior by specifying dynamic default logic.

Note:

Custom segments do not support sourcing for revenue arrangements and revenue recognition journal entries. If you set up sourcing, the value is correctly sourced on the original transaction. However, the value might not be transferred during creation of revenue arrangements or revenue recognition journal entries through Schedule Revenue Recognition Journal Entries and Update Revenue Arrangements and Revenue Recognition Plans. For more information, see Scheduling Revenue Recognition Journal Entries and Updating Revenue Recognition Plans.

For more information about dynamic defaults, see the following topics:

• Dynamic Defaulting for Custom Segments

• Creating Dynamic Default Logic for Custom Segments

• Dynamic Default Values in Custom Segments Example

Related Topics

• Custom Segment Creation
• Custom Segment Types
• Creating a Custom Segment
• Configuring GL Impact for a Custom Segment
• Filtering for a Custom Segment
• Apply to Kit or Assembly Components Setting for Custom Segments and Transaction Line Custom Fields
• Applying a Custom Segment to Record Types
• Validation and Static Default Values for Custom Segments
• User Permissions for a Custom Segment
• Dependent Segments
• Setting Display Order of All Custom Segments

General Notices