In the ‘TAB B LINK’ selection, use the ‘INVOICENUMBER’ selection from Step 1. ![]() In the ‘Record’ selection, use the ID from Step 2. Step 3 - Update Record in Airtable (TAB A) Search by field will be ‘INVOICENUMBER’ and search value will be the ‘INVOICENUMBER’ column from Step 1 (Tick the ‘create Airtable Record if it doesn’t exist yet?’ box if it’s relevant to you) - again, you need to fill the ‘INVOICENUMBER’ record from Step 1 Step 2 - Find or Create record in Airtable (TAB B Info) Step 1 - create record in Airtable (where your Tab A info feeds in) Tab B - you need to look up that column of Record_ID () - called ‘LookUpREC’ - then….Ĭreate a formula column and = the ‘lookupRecID’ column - called ‘LookUpRECString’ Tab A - you need to do a Record_ID () formula - for namesake I’ve called it ‘REC’ Tab A - create a Linked field colum to tab B for the example I’ve called it ‘TAB B LINK’ ‘ INVOICENUMBER’ is in my first column which will be linking tab A to tab B (my unique identifier) I just need some advice as to how I can get Zap to update the Airtable field with multiple values instead of replacing the old values. I want the field to hold multiple entries for the older ones, on the basis of their business name and email. It always replaces the old Requirement links/entries associated with any Client, with the Requirement ID for a new Requirement made by the client. Now the issue is that even thoguh the Requirements column on the clients table is a field that allows linking to multiple data entries, Zap does not update the Requirements column on the clients table with multiple fields. As a result, all the requirements that come through require Zap to be linked from the Requirements table to the Clients table. Since the Client entries are made dynamically, we cannot pre-populate the Client table. Once they put in a Requirement, we use Zap to create a new entry for them in the Client table. The Requirements table receives orders, even from Contacts who are not in our Client list yet. I was curious if anyone had a technical solution for this issue, or perhaps a more logistical correction if I’m thinking about the structure of my base incorrectly.I have an Airtable base with two tables: Requirements and Clients. The simplest solution seems to be somehow adding multiple records from separate integrations to a single field, but that doesn’t currently seem like an option either. That tracks every conversion, but means I have a million columns on my Contact table – and my gallery view (which the recruiters are using) isn’t as clean as I’d like it to be.īecause we deal with thousands of contacts in a year, manually adding each conversion point is not an option. My current workaround is to have a column for every single type of conversion on my Contacts table – which is either blank, or filled with the conversion value (so, a column called General Web Form that receives the value General Web Form if triggered by the integration. Ideally, those conversions would stack up in the same field (linking to multiple records). Zapier can locate the record, and then updated it – but If I use the same trick, the integration will overwrite the existing data in the linked records field, so I lose the General Web Form conversion. The challenge is at the second point of conversion: let’s say Event Registration. ![]() So if a candidate fills out the General Web Form, I can have a unique Zap with the text ‘General Web Form’ dropping into the linked records -> Interactions field and it works like a charm. I have a Contacts table (with Email as the unique identifier), and an Interactions table (with things like General Web Form, Event Registration, etc.). The primary challenge I’m encountering is in logging interactions. We’ve used Zapier for ages to create and update records in Google Sheets, and are shifting our process over to Airtable to allow more users access to the data. Hello! I work in higher ed, and am trying to set up a highly automated CRM base.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |