Hi Chad,
This is Evan with the Quick Base Team and looking over your question and Mark and Avi's feedback I would agree with them. Dynamic creation of fields every time a record is completed isn't something that we would recommend or support. It could lead to a very large number of issues for data integrity, reporting, and performance. Mark's suggestion to have a set number of fields already on the table that are hidden and revealed by form rules is one way of tackling the issue. This way your fields are set and mapped out and just revealed at need. Alternatively, based upon your specific use case, the other option is to create an Approvals table. This table would be the child of your current table and would have a field for Approval, Sign off, and Comments. It would also track the date and time that the Approval record was created, etc. Then you can have a report link that appears on your form that would show each approval related to that Parent Record.
Then each time an approval is needed your users would just press the Add Approval button, create a new approval record, and it would populate in the report. The advantage of this mode is that the Approvals table can accommodate a range of some records needing only 1 approval to other records needing 15 (or more) without the need for fields to be created dynamically at the structural level of Quick Base. If you don't want to use the button there is even an option in embedded reports from another table to allow Editing right in the parent form. So your users would be able to click into a blank line at the bottom of the report and add a new record right there while in Edit mode.
I hope this suggestion is helpful.
