Looking at the available entries under “Player”, the first entry won’t be “Unnamed record” any more, but should match the name of the player I previously entered. I won’t capture the full form here, but the top part will look like this: I’ll then fill out the player’s first and last name, and any stats that I have. Under “Player", I’ll choose the first “Unnamed record” entry that’s available in the list. Let’s say I’m entering data for a football player for the first time. Assuming it all looks good, click “Open form” in the form’s toolbar, which will open the form in your web browser. It should add all of the fields from the main grid view in the same order. Now we’re ready to start talking about how a form fits into all this. As we move on, you’ll see why they need to be there. ![]() You can add them in chunks, or add a ton all at once. The last thing to do in our mirror table setup is add a bunch of blank records to the mirror table. Name it appropriately for your situation. In my case I’ll name this, but I won’t do anything with its fields just yet.īack in the table, insert a new field between the primary field and your first data field, and make it a link to your “mirror” table ( in this example). This will become the “mirror” table, the main place to view all of the data that you collect. Borrowing from the thread that inspired this system, my example setup will focus around stats for football players: After deleting the default records, change the primary field to the Autonumber type, then set up the remaining fields for the data you want to collect. To build this system, the first table to make will be the table. Extending that to allow data from subsequent form-generated records to effectively replace older data in the “mirror” table only took a few more steps. Long story short, the key to that solution was using two tables: one for collecting form data, and another that looks up that form data and fills out a parallel set of fields. However, a base can be set up so that records created by a form end up affecting records in another “mirror" table.Īs with my first show-and-tell submission, this was inspired by a solution that I created in another thread. Technically the answer is “no” because Airtable forms always create new records. (e.g.People sometimes ask whether it’s possible to use an Airtable form to edit an existing record. Ability to redirect users to a custom page after the record is updated.Supports limiting linked record selection to a view.The form requires minimal setup (no need to set up another table nor map multiple fields/select options).Doesn’t require other 3rd party integrations (e.g.Records are updated instantly after form submission.Fields are pre-populated with the existing data before editing. ![]() The ability to limit which fields can be edited. ![]() ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |