Why is the Appeal Segmentation output ignoring the max/nth setting on a segment?

A max/nth is specified on a segment of an Appeal to restrict the number of records returns in the output; the output may ignore this restriction and output the full number of records that meet the segment criteria.
This is a bug, BG 2424203, which will be fixed in a future version.
 

On Appeal Segmentation Entry, when using the max/nth field on segments, if you have multiple segments at a given level, the value you put in the max/nth field to restrict the number of records returned is only applied to the output for the last segment. The counts on the segment will match what the max/nth was set to, but the output file returns all the records that met the criteria. The intended functionality is that the max/nth value be heeded on any and every segment on which it is set.

Visual demonstration:

Segment Level 0
--> Segment Level 1
--> --> Segment Level 2 max/nth 100 - limit not used in output
--> --> Segment Level 2 max/nth 100 - limit used in output
--> Segment Level 1
--> --> Segment Level 2 max/nth 200 - limit not used in output
--> --> Segment Level 2 max/nth 200 - limit not used in output
--> --> Segment Level 2 max/nth 200 - limit used in output


If you only need to have a max/nth on one segment in a given segment level, then making that segment the last one in the group will work.

Environment

 Team Approach
 RSR
 TA

Was this article helpful?