Consider the following:

• Have you assigned at least edit rights to one of your security roles for that page?
• Is it a system table or page that's only available in the setup area?
• Have you already placed it within a page section?
• Have you tried refreshing your instance by pressing Ctrl + F5?
• Have you tried logging out and back into MinistryPlatform?
• Can you find it using the search bar in the navigation menu?

Consider the following:

• Have you cleared your browser's cache?
• Have you tried simplifying your default field list in the setup area so it contains only one field that is directly on your new page or table?

Consider the following:

• Make sure you have properly designated whether this page is a system table or not.
• If it is not a system table, it must have a Domain_ID field.
• Make sure you have a value in the selected record expression. Initially, this value should be a field directly on your table (not an "_Table" Foreign Key). After your page works, you can change the selected record expression to a value on a foreign key table if needed.

Make sure you made the Primary Key of the table an integer value and that Identity Insert is set to Yes with identity seed and identity increment of one. Make sure you have a non-nullable Domain_ID Int on your table. It does not need to be related to dp_Domains.

Try to clear your cache. MinistryPlatform may not yet know one of your new foreign keys. Or, simplify your default field list to where it is just one column from one field on the table itself (not a foreign key table).

Make sure you have a field name from your table or a foreign key table that is datetime type field name in the Start Date field of the page record. The End Date Field is optional.

The field name on the table itself or on a foreign key table that is a Foreign Key to a Contact. If populated correctly, you can deploy many existing reports and specific Core Tools to this page and use them immediately.

Yes, the value that displays in a Lookup field is determined by the Selected Record Expression field on the Pages page in the setup area. This is otherwise known as the "friendly name" that displays in the drop-down list that people use to interact with the data. Here is an example of how this is helpful from one of our churches:

"We use MinistryPlatform for room reservations. We have specific room numbers and we have room names which are more generic. For example, room 312, 313, and 314 are all named 'Classroom', which is fine when picking a room because you can search by the room number. However, once you pick the record, the default behavior is to display the room name of 'Classroom', which doesn't really tell you which classroom you have. There is a field in the page setup record called 'Selected Record Expression' which determines what is displayed after you pick a value for a lookup field. The default for the rooms page is Rooms.Room_Name. We changed it to Rooms.Room_Number + ' – ' + Rooms.Room_Name and now the selected record for a room displays the room number and room name together in a nice readable format (that is, '312 – Classroom' instead of 'Classroom')."

Yes, but keep in mind the following:

• If you change what the GUI shows, it may confuse those who email support as they may not necessarily be aware of the new names and only reference the standard ones in their responses.
• It may also cause slight confusion for your staff as they read Help Center topics, as these only ever reference the standard names.
• Do not change the underlying object names, as this affects views and reports.
• Changing the Display Name changes what displays in the navigation.

The label for a foreign key comes from Singular Name, which you can edit. So, you can modify a page to have a "friendlier" name if needed. Note these concerns before doing this.

The label for the foreign key comes from Singular Name, which you can edit.

If you are going to use the page again with or without modifications in the future, the best way to "hide" it is to remove all permissions to the page from any security roles.

If the record you are trying to save no longer matches the filtered page criteria, you may get an error. Try to open the record on the original page and save your changes.

Ensure that all pre-existing records contain a value in the field you are editing. Specify a default value to use if another application creates the record.

Ensure that the filtered page has a filter in the Filter Clause field.

You add the section header using the SQL table using field type of DP_Separator.

Tool tips come from the field Description on the field in the SQL table.

Your custom tables probably lack a domain_id (int) required field that is Foreign Key to dp_domains.domain_id. This value puts the table in the security scope. Without it, the table is a system table visible only to setup admins.