Prerequisites for Creation of a Dynamic Default
This topic outlines the essential requirements and conditions that must be met for dynamic default values to be generated for custom segments. For general information about dynamic defaulting for custom segments, see Dynamic Defaulting for Custom Segments.
Sometimes you may save a Source List choice, but a dynamic default isn't always generated for the applicable record types. For a default to be generated, the following statements must be true:
-
The source record instance must have a value saved in the segment field - If the segment field on the source record instance hasn't been populated with a value, no dynamic default is created. For example, suppose you have configured the segment on sales transactions to populate with the segment value saved on the corresponding customer record. If the corresponding customer record doesn't have a value saved in the segment field, no dynamic default is created. To avoid this situation, make the segment required, as described in Making a Custom Segment Mandatory.
-
The Source List field must exist on the entry form for the target record type - On the subtabs where one Source List is used for many record types, not all record types have all of the fields listed. If you select an option in the Source List field, and one of the record types doesn't have that field, no default is ever created for instances of that record. For example, on the Transactions subtab, the Source List includes an option labeled Sales Rep (Employee). If you select that option, dynamic defaults are created for transactions with a Sales Rep field. For example, instances of the Cash Sale record type could receive the dynamic default value. However, for transactions such as Journal Entry, which doesn't have a Sales Rep field, no dynamic default can be created.
-
A value for the Source List field must be selected on the instance of the target record type - Sometimes not every field on a record has a value saved. If an instance of the target record type is saved with no value selected for the field identified by the Source List, no default is created. For example, suppose you have configured account records to populate with a default value. In the Source List for the Account record type, you may have selected Restrict to Location (Location). If an instance of the account record doesn't have a value selected in the Restrict to Location field, no dynamic default can be created for that record.