How chunking in tables works

Cell-based tables and list view tables support chunking to return all records while limiting the number of records displayed at one time. The chunk control contains a drop-down menu, navigation buttons, and a results string.

Application developers can remove chunk control from the table header by setting the Next Label and Previous Label properties to an empty string or by setting the chunk size to 0.

The chunk control appears on the left of the table header. Following are the appearance and behavior of the chunk control:

• The chunk control drop-down menu displays the record number (starting and ending record number of the chunk being displayed), and not the page numbers. For example, when you set the chunk size to 10, and navigate to the second chunk, the chunk control displays 11-20.
• The Number of Entries Returned property in Remedy Developer Studio is set to {2} of {3} results, by default.
  • When chunking is not enabled, Mid Tier interprets the parameters and displays both the total number of rows returned and also the maximum number of rows that can be returned.

  • When chunking is enabled, Mid Tier interprets only the {3} parameter.
    When chunking is enabled for a table and the matched result count exceeds the chunk size, the chunk shows a count that is the sum of the entries visible in the current chunk along with the entries in the previous chunk. This continues till the last chunk is traversed from the lowest to the highest chunk.

    When the last chunk is processed, all records that are accessible to the user are obtained based on their permissions and you get an accurate count of entries matched. This count does not change even if the chunk is traversed again.

  • 
    

    You can add an additional parameter {4} to the Number of Entries Returned property. For example: Number of Entries Returned = {2} of {3} results {4}. Mid Tier interprets the {4} parameter and based on the number of records returned, the value set for the Row label or Row label Plural property appears on the table header.

    • If the table contains only one record, the value set in the Row label property appears on the table header.

    • If the table contains more than one record, the value set in the Row label Plural property appears on the table header.

      If the number of records in the table is less than the chunk size, the chunking control will not be visible.

• The number of entries displayed on chunk control is right aligned.
• The results string that displays the total number of records in all chunks appears on the right of the chunk control.
• The Page label is removed from the table header.
• The navigation control to move to the previous chunk and the next chunk always appears with the chunk control.
  • When you have selected the first chunk, the pagination control to navigate to the previous chunk is displayed in the disabled state.
  • When you have selected the last chunk, the pagination control to navigate to the next chunk is displayed in the disabled state.

Screen updates due to adding or deleting rows

The following examples show how chunks are displayed when records are added or deleted. (Although you can add or delete rows for cell-based tables, the recommendation is not to add or delete rows with content clipped cell-based tables.)

If a user adds a row (the following figure), then requests the next chunk, the next chunk of records displays starting with the next record that was not visible. 

Example: Next chunk displays after adding row then requesting next chunk (chunk size of 8)

If a user deletes a row (the following figure), then requests the next chunk, the next chunk of records displays starting with the next record that was not visible.

Example: Next chunk displays after deleting a row then requesting the next chunk (chunk size of 8)