2021.1

l Through a Post Pagination script in the template. (See "Post Pagination Scripts" on
page919 and "contentitem" on page1423.)
Sorting by property is only possible if the property has been set explicitly on the respective
content items (not content sets) in the Connect database.
It is also important to note that in order to use a data field or property in a sorting rule, it should
be present in all content items.
You may have to set properties on content items (not content sets) or add data fields to a data
model (see "Data mapping configurations" on page197), for no other reason than to sort the
items by them eventually.
In Connect there are two places where you could group and sort print content after it has been
retrieved from the Connect database:
l In a Job Creation Preset.
l On the Batching/Commingling tab of the Retrieve Items task.
Job Creation Preset
Based on the settings in a Job Creation Preset, the Connect Server can filter, sort, and group
print content items, add meta data and make finishing settings (see "Job Creation Presets" on
page1456). Compared with the Batching/Commingling tab of the Retrieve Items task, a Job
Creation Preset offers a lot more options. It is also usually more efficient; that's why it's the
recommended method, for larger jobs at least.
A Job Creation Preset can only take content sets as input. So, if you want to use a Job
Creation Preset, the Retrieve Items task must retrieve content sets from the Connect database,
not content items.
This also means that if you want to use properties in conditions to retrieve the correct items,
those properties must be set on the content set level.
However, any properties that you want to be used for filtering, grouping or sorting must be set
on the content items.
Batching/Commingling tab of Retrieve Items task
The Batching/Commingling tab of the Retrieve Items task allows you to group and sort print
content on two levels. You can:
Page 194