![]() I want to get this into Airtable and keep the current membership number as the primary field so that it auto increments when a new record is added. Hopefully this helps other folks in the future! Thanks so much. I currently have a membership database in ACCESS and the membership number is the primary key. Tl dr: Apparently zapier cannot zap data into linked fields WHEN those fields/columns originate, at root, from other Airtable bases than the one being zapped into. It’s unfortunate that I will have to enter the contact and location manually (by picking them from my linked list from another Base), but overall it’s not that big of a deal. Now that you’ve completed these three steps, you. Finally, you leveraged your relationships to easily find relevant information and reduce manual data entry. Then you created the relationships to link related information. You can match records from your source to your Airtable workspace by the tables primary key or any other unique fields in the table. Update: updates particular fields on existing objects in Airtable. Once removing those two fields from my output (a Contact field and a Location field), the Zap worked correctly. You’ve taken three key steps to linking records in Airtable : You defined how your workflow’s information is related. Upsert: pushes new objects to Airtable and updates fields that change in your warehouse. If the record is deleted, then the value will be the delete timestamp - the time when the record. (For example, I was outputting a ‘First Name, Last Name’ into an Airtable field that was synced in internally from another of my Airtable bases, titled “People”.) record with the same primary key minus one millisecond. However, I realized that there’s another way to interpret “external sync”: as fields within my output Zap that are linked fields dependent on external Airtable bases. By choosing 'Date', for example, since me primary field is not a date, the Primary Field will now be EMPTY. BUT, for some reason, you can change the TYPE of this field. On the synced table in the new base, you'll get the same Primary Field. So I tried creating a new Airtable connection and rebuilding the Zap from scratch-and that did not work. The trick is to create a new base, and sync the table you want to share. ![]() Thanks so much for the quick reply, it took me a bit to get back to this problem.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |