Apr 11, 2024 01:38 AM
Hi Airtable Community,
I have a table with events. New events can be added via a form and various needs can be requested for the event using a multiple selection field.
A record is generated in a second table for each need.
I have currently created an automation for each selection option as I have not yet found a way to do this dynamically. However, as there are now around 30 different needs, I would like to make the automation dynamic. Any ideas for a solution? The problem is that the need has to be named correctly and I can't pull this information dynamically from the multi-selection field.
Thank you and Best
Mirko
Solved! Go to Solution.
May 03, 2024 09:10 PM
re: But is this also possible with a multiselect field. Otherwise the users cannot choose from a list, but request what they want.
I don't think so I'm afraid, you'd still need to use an automation to create one record per multiselect option
---
It seems like you really want to let your users use a multiselect field instead of a linked field, and you also cannot get your users to stop submitting requests for needs they've already asked for in the past
If so, I think a possible option is to use a formula field to output a unique text string per Event and Need combination, which can be seen in the field "Text for pasting" below:
You can then use an automation that will paste that output into the linked field, which will do what you need
Apr 11, 2024 01:41 AM
Try using a repeating group action, using the multiple select field as your input:
https://support.airtable.com/docs/repeating-groups-of-automation-actions
Apr 11, 2024 02:02 PM - edited Apr 11, 2024 02:03 PM
I think it would save you a lot of time and headache and give your users a better user experience to by using Fillout in conjunction with Airtable to accomplish this workflow. With Fillout, you can have the user create linked records so you don't have to worry about making a long, convoluted conditional or repeating automation. Also, the form styling is modern and up-to-date. Let me know if you need help with this!
Apr 29, 2024 08:06 AM
@TheTimeSavingCo thank you for your message. That works fine. However, I still have a problem:
For some of my requests, I also have a comment field in the form. this comment field, must also be inserted in the created requests. So if someone selects Watchmaker in the multiple selection and enters something in the comment field, I want a data record with the name Watchmaker to be created in the Requests table that is linked to the respective event, and the comment from the comment field to appear in the Comment field in the Request table.
Any ideas on how to solve this?
Thank you and best regards
Mirko
Apr 29, 2024 07:09 PM
Hmm, I think you'd need to:
1. Create one lookup field per type of comment in the "Request" table
2. In "Request", create a formula field that will display the value of the appropriate lookup field based on the selected staff need
Apr 30, 2024 01:24 AM
@TheTimeSavingCo thank you!
That works well. But I still have the problem that if I subsequently want to set another need, the automation is retriggered and all requests are generated again. I'm beginning to think that the only way to solve this is with individual automations for each need.
Apr 30, 2024 04:08 AM
Interesting! Assuming you've already submitted a need for a Watchmaker and you find that you now also need an Engraver, are you saying that you are submitting a form with both "Watchmaker" and "Engraver" selected?
Apr 30, 2024 04:21 AM
Exactly. It may well be that only one watchmaker is planned when the event is first planned. It is then decided later that an engraver is also required. The users only have access to an interface in which they cannot add new entries manually but can open the respective event data record and generate a new record in the "Request" table by selecting the additional needs in the additional selection field.
Currently, the automation that generates a new request is triggered when, for example, "Staff Needs" is updated. However, all options clicked on are then generated. Regardless of whether they have already been created.
Best
Mirko
Apr 30, 2024 10:22 PM
Hmm, if it's possible to change the workflow so your users don't select needs that they've already previously selected that would be the simplest option
If that's not an option, I'd suggest looking into Fillout. It's possible to do this natively in Airtable but it's a fair amount of work, so might as well just use Fillout I reckon
May 02, 2024 04:54 AM
Thanks for your message.
I have had a look at Fillout. But the way I see it, that won't meet my needs either. It would work fine for the initial creation of the requests, but if I want to add some Needs later, Fillout can't really help me either, can it?
Best regards
Mirko