Many types of forms that can be created in Air Maestro make use of tables. These frequently vary in the number of rows according to the requirements of that particular form. At the moment the only way to accomplish this is to create many duplicates of any field in the table and hope that you have created enough rows to meet any future requirements.
The other issue is that any fields that need to be edited need to be edited several times to prevent inconsistencies between rows.
Examples of tables that I have recently created are here and here.
I propose a new custom field control type called table with the following features.
The ability to create column headers.
The ability define the number of columns
The ability to select from other custom field types for each column.
The ability to perform functions such as count rows, sum, average, etc in the table footer.
I have created a proposed mockup of this control here. This would look like this in practice.
This would have the advantage that there are a single set of custom fields to maintain and the number of rows can be adjusted on the fly. For example; the dropdown lists in the 'Handling' example all have 'Allow Custom Text' enabled as new information is required. The new entries are not synced between all of the dropdown lists available and will have to be entered manually in each row at least once.
I believe the major technical issue is that each custom field has a unique ID which can be referred to elsewhere. Two options to work around this would be to have an ID hierachy such as is present in the flight records where each flight (table control) has a unique ID and each leg in that flight (row in the table) has it's own ID. For the table, this would probably be up to an arbitraty limit limiting the number of rows that can be added per table.
The other proposed solution would be to make the functions in the footers act as calculated fields with their own unique ID which can be referred to elsewhere.