Hi @Cole_Wedemeier and welcome back to the community.
I don’t know why u are using a Zap for this (there could be a logic reason), but via the Airtable automations, when you use a new option in table 1 (new lead with new source) to create a record in table 2 (all leads) with that new option, it will just add it as an extra option in your multiple select field.
In an Aitable automation you’d insert the record’s current value as pulled from the trigger record (or some earlier step), add a comma, then add the “new” value. I assume its the same for Zapier.
Hi @Cole_Wedemeier and welcome back to the community.
I don’t know why u are using a Zap for this (there could be a logic reason), but via the Airtable automations, when you use a new option in table 1 (new lead with new source) to create a record in table 2 (all leads) with that new option, it will just add it as an extra option in your multiple select field.
The lead is being captured outside of Airtable, so the zap is required to put the information gathered in one platform into Airtable. I don’t have an issue creating a new lead source, as it’d only have one at that time. It’s when the find record locates one and then goes to input the new source. That’s when this multiple select field gets overwritten from any of the other sources it might be displaying to only show the one the zap is trying to input (instead of adding it).
In an Aitable automation you’d insert the record’s current value as pulled from the trigger record (or some earlier step), add a comma, then add the “new” value. I assume its the same for Zapier.
@Kamille_Parks this is exactly what I had to do. Thank you! The only item that needs to happen before this, is to ensure that there is a test subject within the steps to find that already has a source listed. otherwise, if the first step of find record returns false, and creates the record for you, the multiple select field does not show as an option for putting what was found followed by a comma and the new information you want to add.
I appreciate your answer, thank you again!