System Development, Software Updates, Quick Guides and Builder Training InformationBuilder Site Help Documentation Turning a field into a Table or MatrixTables in Your Forms. Examples of basic tables, tables that include databases and tables that link to other forms (e.g. 1RM results)

Tables in Your Forms. Examples of basic tables, tables that include databases and tables that link to other forms (e.g. 1RM results)

Tables are used to capture and plan any type of information from Strength and Conditioning sessions, through to capturing family history of disease or physiological tests. All of the fields that are available on the Add Question Tab on the form Builder can be used as single fields, or as part of a table.  Tables allow you to capture and plan for multiple data sets for one variable/field.

Before you start to create a table in your form, it is always import to think about the data you are capturing and plan it on paper first. Once you are happy, then build the table.

Before you start to create a table in your form, it is always import to think about the data you are capturing and plan it on paper first. Once you are happy, then build the table.

Tables are used to capture information that requires multiple values for a single Field. They can ONLY be built in a Column format (if you require a row based table, you might consider building a Matrix). The image in the example here shows an image of an injury assessment table where the field names have been turned into a table columns that captures the date of assessment (date field), subjective, objective, treatment and action information (paragraph of text fields), and also who entered the soap notes (entered by field).

Building a basic table: a hospitalisation table example

Building a basic table: a hospitalisation table example

The example here shows you that a table has been set up on a profile form to capture hospitalisation information using a date field, option fields, numbers and text fields.

 

To build a table, click on the type of field that is going to be the first column in the table. In that field's Question Settings, change the Entry Mode (circled) from Normal to Table.

To build a table, click on the type of field that is going to be the first column in the table. In that field's Question Settings, change the Entry Mode (circled) from Normal to Table.

For this example we are using a date field that is going to be used to track "Date of Hospitalisation"

Once you click "Table" the question will then automatically form a column with 10 rows

Once you click "Table" the question will then automatically form a column with 10 rows

For the First field in the table in that field's advanced properties, you can specify the number of table rows that you want to appear on the form during data entry. For this example we are going to limit the table to 3 rows

For the First field in the table in that field's advanced properties, you can specify the number of table rows that you want to appear on the form during data entry. For this example we are going to limit the table to 3 rows

For this date of hospitalisation field, go to the advanced properties and limit the rows from 10 to 3 and the rows that appear will be limited to 3 (as shown in the image in the step below).

That field is set up as a table in the event form and multiple dates can be captured. We limited the table rows to 3, but users can always add additional rows using the "Add rows button" (shown here)

That field is set up as a table in the event form and multiple dates can be captured. We limited the table rows to 3, but users can always add additional rows using the "Add rows button" (shown here)

To add additional fields to the table, select the type of field that you want and add it to the form. It should automatically be added to the table, but in the field's Question Settings, you can set this to table. Each field that you add will be added to that initial table

To add additional fields to the table, select the type of field that you want and add it to the form. It should automatically be added to the table, but in the field's Question Settings, you can set this to table. Each field that you add will be added to that initial table

If you add a new question directly after the first table column, the new question will automatically appear as a column field with 3 rows. For this example we are adding a reason for hospitalisation field which is a text field.

The example here shows that a Line Text (Reason for hospitalisation), Yes/No (surgery performed) and Number field (days in hospital) have been added.

The example here shows that a Line Text (Reason for hospitalisation), Yes/No (surgery performed) and Number field (days in hospital) have been added.

We can also add in a Table Calculations underneath the table to Sum the days in hospital or number of surgeries.

We can also add in a Table Calculations underneath the table to Sum the days in hospital or number of surgeries.

Total Days in Hospital is a Table Calculation field, that was set as a Sum. So was the Total Surgeries field  (see the step below for more details).

Table calculation for Days in Hospital was set up using a Table calculation and performed by selecting the Aggregate "sum" for the field "Days in hospital" (this will sum all numbers in the Days in Hospital column)..

Table calculation for Days in Hospital was set up using a Table calculation and performed by selecting the Aggregate "sum" for the field "Days in hospital" (this will sum all numbers in the Days in Hospital column)..

Table with a Database: You can also create tables that include a database where the database fields are also used to fill other columns in your table

Table with a Database: You can also create tables that include a database where the database fields are also used to fill other columns in your table

The table in the image here shows a resistance training event.

This table includes 10 fields that are set to track and manage strength training data:

Exercise: A Database field that is set to a pre-built database called Exercises

Type: Is a text field that is set up with exactly the same name as the descriptor from the Exercise Database

Equipment: Is a text field that is set up with exactly the same name as the descriptor from the Exercise Database

Sets: Number (Format 0)

Reps: Number (Format 0)

Weight: calculation of 1RM * %1RM

RPE: number with min 1 and max 10

Load: Calculation (Reps * Sets * Weight)

Total Session Load: Sum (Load) is a table calculation

Total Work Time: Sum (Work) is a a table calculation

To build this table, the First table field is a database. Select database from the question options. Set the Question settings to "Table" and tick the group by box which will allow you to search your database list in the athlete history and reports modules

To build this table, the First table field is a database. Select database from the question options. Set the Question settings to "Table" and tick the group by box which will allow you to search your database list in the athlete history and reports modules

Add in a database field, set it to a table and group by, then set the number of rows you require and any other advanced properties for that field

Then set up additional rows for the Type and Equipment (which have been set as summary fields on the actual database template)

Then set up additional rows for the Type and Equipment (which have been set as summary fields on the actual database template)

Double check the Database names that you want to automatically pull into the form. The Type and Equipment field are exactly the same as the database. The Exercise name is set up as a Group By

Double check the Database names that you want to automatically pull into the form. The Type and Equipment field are exactly the same as the database. The Exercise name is set up as a Group By

The image here shows the structure of the Exercises Databases (an image from the database module on the builder site) to highlight the type of database that has been added into the Resistance Training Form.

Set up the rest of the table column fields such as reps, sets weight and then save the form.

Set up the rest of the table column fields such as reps, sets weight and then save the form.

Add in additional fields such as sets, reps, rpe, weight etc as required.

Now in the actual application enter data for that form and check that when you choose a record from the database that the Type and Equipment fields are populated (e.g. when Exercise is selected, the Type and Equipment Field are automatically filled) and that the data flows correctly.

Now in the actual application enter data for that form and check that when you choose a record from the database that the Type and Equipment fields are populated (e.g. when Exercise is selected, the Type and Equipment Field are automatically filled) and that the data flows correctly.

Check to see that you have set up the table correctly on the enter data page and in the athlete history and the reports pages to see that they appear there as well

Once data is entered into the event a user will be taken to the athlete history or reports page. In the athlete history and reports, the field rows from the table will appear as separate rows on the reports as shown here

Once data is entered into the event a user will be taken to the athlete history or reports page. In the athlete history and reports, the field rows from the table will appear as separate rows on the reports as shown here

For one record (e.g. one resistance training record) that has 6 exercises entered into it, that will take up 6 rows in the athlete history page and reports pages. If you do not want the table rows to take up separate rows in the athlete history, then each field in the table needs to be set to default show in table =false (in the advanced properties). The example in the image below shows that the table were set not to show and one strength training record only takes up one row on the athlete's history. You can always click through to see the reps and set etc.

If the Table Columns are set to "default show in tables=False" each event record only takes up one row in the athlete history and reports modules (as opposed to the number of rows that are entered in the table)

If the Table Columns are set to "default show in tables=False" each event record only takes up one row in the athlete history and reports modules (as opposed to the number of rows that are entered in the table)

0 Comments

Add your comment

E-Mail me when someone replies to this comment