Automation to create record if does not exist
I have a Request table, and when a new request is entered, certain values are then taken to create a new record in Table B... issue is that I'm hoping to only have the new record in Table B to be crea...
Forum Discussion
The difficulty is that there's no direct relationship between these two tables... We purposefully did that to avoid the "one-to-many vs many-to-one" relationship conundrum... as multiple locations can be made from the same request.
- It is not ideal, but if a webhook fails because it cannot create a record, due to duplication; it will simply fire out an email. I suffer these for the convenience of having a custom key field in a parent table created from (in my case) a set of child records which auto-create the parent record the 1st (and only time). Building a connection simply to prove the parent already exists but not for any other purpose is still worth building a relationship; and to prevent webhooks from firing multiple times when you know they will fail. You may get one or two emails if records are added close together; but once the parent-connection proves itself you will avoid being inundated with failure emails.
Your alternative is to use Google Scripts to create these "parents"; which will still only create records when the Key is unique and does not already exist.
