![]() I’ve tried to make sense of each of these two solutions, but I can’t quite make sense of it. I want the new parent form submission to show to be linked to the player, but not remove the existing link to another parent. It then updates the link for the player to parent to only show the link to the newly arrived parent. However, if a player exists and is already linked to a parent, and then I add a new parent who links to an existing player, it takes the existing link between the player and existing parent and destroys it in what I imagine is a fiery, painful death. ![]() If a parent already exists in the database and is already linked to a player, when I add a new player through the form who is also linked to that same parent (think a sibling of the existing player), it works successfully and the parent record now shows it being linked to 2 player records. ![]() Much to my misery, I find out that I cracked open the six-pack a moment too soon. So I’ve turned on my zap, everything seems hunky dory, I’m sucking back on a few beers feeling good about myself as I do my ‘final tests’. If they are a parent, the zap will add/update a parent record, and then add/update a player record. If they are a player, the zap will only add/update a player record. That info is then used to filter the zap. ![]() The form asks if the person filling out the form is a player or a parent. I have created a zap that distributes the data from a form to my airtable database. Players can be associated with multiple parent records, and parents can be associated with multiple player records. My airtable database is setup with players and parents tables. That’s it! I told you it wasn’t complicated :) It’s one of those things that clicks when you see it, but if you haven’t considered it before then it will have felt like an impossible task.I’ve been wrestling with a problem the past few hours and have decided it is time to ask for help. Map any other fields that you might want to update (either using the method above, or by using the value that comes from your trigger).That simulates keeping what’s already present, then you also map the field from your trigger that contains your new data. Next you’ll map the contents of the field you want to update (from the search step), into the field you want to append text (in the update step).Here, you should be able to use something from your trigger step in order to find the item you need (like an email address, name, etc). Add a search step in between your trigger and your update action.But if you tried to map a field from your trigger step into the Description field, it will overwrite what’s already there instead of adding it onto the existing text. Now, it’s nothing revolutionary to tell you that in order to update an item in your app you’ll need an Update action. If you wanted to update a Description field for someone in your CRM, you would need something like Find Contact and Update Contact. And you’ll also need an Update action (as opposed to just a Create action). The way we do it is by first looking up whichever item you want to update, so if the app integration doesn’t have a search action that supports that, I’m afraid you won’t be able to use this workflow. you have a Description or Notes field in your app and want to add to it instead of replacing the existing textīefore jumping into the details of how to accomplish this, I do want to offer a couple of caveats.you’ve got a CRM and would like to record each time a customer purchases something from your online store.Luckily, when it is possible, it’s not actually that difficult to do.įirst, let’s look at some examples of when you might want to do this: A lot of users ask whether it’s possible to append data into a field instead of overwriting existing data, so I thought I would break that down a bit.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |