My problem: BarTender prints the same label over and over. My observation suggests that it is using total number of rows in the source data to determine total number of printed items (labels).

I’m looking for help understanding how BarTender 12 determines printed items when using a table‑driven, multi‑row template.

Scenario

• BarTender version: BarTender 12
• Label template contains: 
  • One table object with 15 rows × 4 columns
  • Each column is bound to a database field
• Database settings: 
  • Data source is CSV via Text Database connection. Single record, no joins
  • Maximum number of records per printed item = 15
  • Combine multiple records into a single field is enabled
  • All fields are included so that multiple records render within the same table

Test Data

• CSV file with 15 data records
• Each record represents one logical “detail line”

Observed Behavior

• When running a test print from Designer: 
  • The table renders correctly with 15 rows populated
  • However, 15 identical labels are printed, each containing the same 15 rows

If I modify the CSV to contain 16 records and reprint:

• BarTender outputs 16 printed items total 
  • 15 identical labels containing rows 1–15
  • 1 additional label containing row 16 repeated 15 times

Expected Behavior

I would expect BarTender to paginate the data based on the “Maximum number of records per printed item” setting:

• Page 1: records 1–15 (one label)
• Page 2: record 16 only (one label, not repeated)

Current Interpretation

It appears BarTender is using the total number of records in the data source to determine the number of printed items, even though the table is configured to consume multiple records per item. I’m trying to understand how record iteration and printed‑item calculation are supposed to work in this scenario, and whether additional configuration is required to achieve paginated output rather than repeated labels.

Is this behavior expected in BarTender 12, and if so, what is the supported approach for generating paginated, table‑driven labels from a single dataset?”