Connections enable you to create an interface that works more like a website than a database.

Example

With our contact directory example app we don't need to view all the contacts for every company in one table. It may be more intuitive to first select a company:

And then view all the contacts connected to that company:

How To

1. Adding Views for Connected Child Records

2. Creating Edit and Details Pages

3. Adding Forms to Add a Connected Record

Adding Views for Connected Child Records

You can show any child records like this by selecting the Table option at the top of any details or edit page. See below if you need to create a details or edit page.

Knack will automatically know that you have connections to the current object and present options for displaying views for those connected objects:

Any connected objects are presented under the "Records connected to this page's Company" section. Selecting a child object displays options to add views for those connected child records.

You can continue to build a hierarchy of connections like this. For example, we could show all the note records that are connected to each contact. You will see the option to add that under the "Records further connected to this page's Company" section:

Creating Edit and Details Pages

Edit and Details pages are created from views that display multiple records, like tables, lists, or searches.

The idea is that the user will click on one of the records displayed by those views to edit that record or view more details about it.

Each view has options to add these links automatically. For example, a table has a special "Links" tab above the list of fields in the left menu you can click to add these links:

When you save that table, a new child "Details Page" will be automatically created. You can then click on that new page to add views for connected records.

Adding Forms to Add a Connected Record

When you add a form to add a connected child record, Knack will automatically connect that new record to the current parent. You don't need to have the user select the parent in the form.