Sub-Pages appear at the bottom of a Page in the row of tabs. They can be filtered using Sub-Page Views.


Sub-Pages cannot skip a level in the hierarchy between Page and Sub-Page. The tables for the page and sub-page must be directly related (without another table in between). The relationship between the two must conform to one of the relationships defined below under the Relation Type field. See Relation Types.

Sub-Page Fields

The following fields are available on the Sub-Pages page in System Setups > Sub-Pages.

  • Display Name: A plural text value used as the label to identify to end users the types of records accessible from this sub-page.
  • Singular Name: A text value used to identify the type of a single record visible in this sub-page.
  • Page: The page under which this sub-page will appear.
  • View Order: Sub-pages under the same page appear left to right based on this order.
  • Link To Page: The page to which a user navigates if they click the blue link icon in a row on the Sub-Page grid. User must have at least Read permission to the linked page to see the navigation link. This can not be a filtered page (if one is used, navigation goes to the unfiltered page).
  • Link From Field Name: The name of the INT field on the table associated with this sub-page (see the Primary Table field below) that stores the value of the record the user would navigate to when they use the blue navigation link icon on the left of the subpage record.
  • Select To Page: The page listing records being added to the sub-page in a many-to-many situation. The pick list for the Add Button launches this page. This can not be a filtered page (if one is used, navigation goes to the unfiltered page).
  • Select From Field Name: The fully qualified (table.column) name of the foreign key column on the sub-page's table (see the Primary Table field below) that references the other table in a many-to-many relationship.
  • Primary Table: The name table object in SQL Server that stores the records visible in this sub-page.
  • Primary Key: The name of the primary key column on the primary table that stores the records visible in this subpage.
  • Default Field List: The columns on this and related pages (tables) that will appear in the "all records" grid view.
  • Selected Record Expression: The columns which describe a single record on this page
  • Filter Key: The column on the parent page by which the records in this sub-page are filtered. This has to be a Primary Key or Foreign Key depending on the Relation Type.
  • Relation Type: A selection that indicates to the Platform what type of relationship this Sub-Page has its parent Page.
    • Many to One: Filter key is foreign key on the parent page, sibling records to be shown. See Many-To-One Relation Type.
    • Many-to-Many: Filter key is a foreign key on the primary table (see the Primary Table field above) that stores cross-referenced records on the select from page. See Many-To-Many Relation Type.
    • One to Many: Filter key is the primary key of the Page this Sub-Page will appear on. See One-To-Many Relation Type.
    • Recursive: Filter key is a foreign key on the parent page's table that relates back to another record's primary key on the same table. See Recursive Relation Type.
  • On Quick Add: When set to true, users with Quick Add rights to the parent page can add sub-page records using the Quick Add tool.
  • Contact ID Field: The column on the table that leads back to the contact record associated with this record. Used by existing reports and tools. The Contact_ID can be found several tables removed via foreign keys and the "_table" lookup convention. A value here includes the sub-page in Select Message Recipients.
  • Default View: A sub-page view record explicitly associated with this sub-page that is presented to users when they arrive on this sub-page in lieu of the all records view.
  • System Name: A field used internally by the Platform. Not for use by third parties.
  • Date Pivot Field: A field on the primary table or a related table, generally text, that is visible in the timeline view for Group records.
  • Start Date Field: The column that holds the starting DateTime value for a record visible in the calendar, gantt and timeline views.
  • End Date Field: The column that holds the ending dateTime value for the record that is visible in the calendar, gantt and timeline views.
  • Custom Form Name: A field used internally by the Platform. Not for use by third parties.
  • Display Copy: When set to true, values in this sub-page can optionally be copied by an end user when copying the parent record.
  • Messaging Default: When set to true, this sub-page will be pre-populated  - along with it's Default View if set - in Select Message Recipients when the New Message Tool is launched from a selection on the parent page. 

Sub-Page Permissions

Once you create a Sub-Page, remember to grant users permission through a Security Role. Best practice recommends always adding new Pages and Sub-Pages to the default Administrator Security Role first before granting permission through additional Security Roles. 


Last Modified: 10/29/2019

Did this article help?
× Thank You for the Feedback