Changes that Can Indirectly Modify the Type Field of a Segment
This topic details scenarios where a custom segment's type might be changed indirectly because of how segments are used in filtering relationships. For an overview of custom segment types and additional considerations, see Custom Segment Types.
Be aware that in some cases, you can indirectly change a segment's type. For example, this type of change can occur when you have a filtering relationship between two segments, one of type List/Record and one of type Multiple Select.
For example, suppose that Segment A is of type List/Record. You may decide to filter Segment A's values by the choice a user made in another segment, Segment B, on the same record. Suppose that Segment B is of type Multiple Select.
With filtering, both segments must be applied to the same record types and transaction columns. So in this example, you're choosing to filter Segment A's values according to Segment B. In this case, if Segment B isn't already applied to the same records as Segment A, the system makes changes. It automatically updates Segment B to apply it to all of the records where Segment A has been applied.
Now, suppose that Segment A has been applied to a transaction sublist, such as Sales Item or Expense. In this scenario, when you create the filtering relationship between Segment A and Segment B, the system must apply Segment B to the transaction sublist that Segment A is associated with. However, because a segment of type Multiple Select can't be applied to transaction sublists, the system changes Segment B's type to List/Record. In this case, you're not warned that the type of Segment B will be changed.
For more details about filtering, see Filtering for a Custom Segment.