Understanding the page concept in Helix is important for proper application of the Visibility and P# is Page Number attributes. These two attributes do not follow the same set of rules. This technote seeks to clarify some common misunderstandings.
These are the specifications related to page numbering in Helix:
- On a list, a label rectangle with the P# is Page Number designation turned on functions as a simple line numbering mechanism, and that numbering carries forward across multiple pages. (See the view Sub As List below.)
- On a subform, all P# is Page Number designations draw their value from the host list’s page number. (See the view Host List below.)
- On an entry view, the outer form page number is always ‘Page 1’.
- The Set Starting Page# command can designate a different starting page number, but that is still considered ‘Page 1’ for the purpose of applying these rules.
Conceptually, when Helix determines whether items should be visible on the first, interior and/or last page of a list, it is the template directly attached to the view it is considering. Inner (subform) templates are not considered as separate entities for the purpose of determining visibility. As these pictures show, both the list (the main template) and the subform (the embedded template) derive their first/interior/last value from the outer template.
Whether the listed items are on the outer list or an inner subform, the visibility is controlled by which page they are on. (You can identify the page breaks by the horizontal light gray lines. Despite its small size, these views would print on three pages, not one.)
As this picture shows, the concept of page numbering is not the same as that of first/interior/last page.
Unlike the first picture, this template is not trimmed so that each iteration of the outermost template occurs once per page. As a result, two iterations of the outer list appear on the first page.
Although the visibility appears illogical, it is correctly following the Helix specification. Unlike the first picture, this view only has two pages, as this view is able to show two iterations of the list per page.
When using the visibility and page numbering attributes, be sure to keep these distinctions in mind.
P# is Page Number
Usage: marks a label rectangle so that the characters ‘P#’ will translate into a page number when viewing or printing a form.
When: a template is the active window and a label rectangle or the label rectangle tool is selected
When working in a template, any label rectangle can be given the P# is Page Number attribute. Wherever ‘P#’ appears in a label rectangle and the P# is Page Number command has been selected for that rectangle, a page number appears when the form is displayed on a view.
Note: An uppercase P must be used, and there must be no space between the P and the number sign (#).
Tip: When placed inside a repeat rectangle, the P# is Page Number command will provide ‘line numbers’ (except on a subform).
Label Rectangles
You can number each record on a listing form by placing the P# label rectangle inside a repeat rectangle. If the P# label rectangle is outside of the repeat rectangle, Helix numbers each separate page. A form can have a P# Label rectangle outside the repeat rectangle and one within it, although the starting page number is the same for both. (See section 4.5.7.)
Page Numbers
On subforms, page numbers inside the subform do not increment for each new line. They increment with each record represented by the outer form.