Using Forms for RFI?

Thanks Bill. Looks like that would work. Not sure if it saves any time or not, but good to know about it!

Well, imagine a system where the data you capture in a record is a waypoint for yet another form entry - i.e., the record itself creates a URL that becomes another process step for the same form. Except, the second step in the workflow (a new URL to the same form) includes the field values entered thus far; it has all the data you added. The URL that’s generated is then shared in some automated fashion to the person who needs to complete the form. When they open it, the fields you wanted to be prepopulated are filled in.

This approach is how you create workflows and workflows create seamless progressions where people needn’t enter the data a second time; that’s how it saves time and it seems that this is what you needed, right?

One recommendation, sketch your workflow; it will help you discover opportunities to save time and streamline the process. Sharing it here will only make it easier and more likely to energize some forms-handling ideas from the community.

Thanks Bill! I had to read that a few times, but I got it to work… partially. I can get it to redirect to the same form with the specified fields prefilled, but they are prefilled with the literal record id. Should I be using something other than “Record Name”={record_id} ?

Um, yes. Perhaps something like:

“Field Name”={Field Name}

Where “Field Name” is an actual field in the form/table.

can you share the full syntax? Where does the reference to the Record ID for the partially completed form go?

Thanks.

The syntax depends greatly on your solution; can you share some of that so I can see what we’re building?

I’m certainly no expert in form-building matters, but I think this is natively possible.

• Is it not possible to create a dynamically populated URL to the form in a record?
• Isn’t it possible to take that URL and establish access in a view? Or send it via a block?

MiniExtensions might make it easier, but I don’t think native Airtable is incapable of workflow steps that are centric to a single form that reaches milestones where fields are increasingly more populated.