I’m using Interfaces and Tables to build an application form for a scholarship. As part of the scholarship, we are collecting CV/resume data. Our plan is to use a form with fields for the CV/resume information versus having them upload a PDF resume. We want a consistent data structure for the information so we can use a rubric to score it.
I’ve built a big table to support this with a bunch of fields like “Educational Institution 1 Name”, “Educational Institution 1 Location”, etc. The idea was to build a form or a series of forms that applicants could use to enter their data. However, working with a large table in the form builder function is challenging. If I create a form linked to the table, it pulls over ALL the table fields, which means I need to go through and delete the ones I don’t need.
In addition to being tedious, I keep getting database errors as I delete the form fields. Everything seems like it is working correctly but it makes me nervous.
I went with one big table versus a number of linked smaller ones based on a suggestion from ChatGPT (:shakes fist at ChatGPT:) - it seemed easier.
Is there a better way to work with a large Table in the form builder for Interfaces, or should I bite the bullet and break it up into smaller linked Tables? I’m still early enough in the project that now would be the time to do it.