I am using Make.com (formerly Integromat) to automate sending emails for a licensing workflow. The main S123 table is a personal info table (name, employer, etc.) and information for individual licenses is stored in repeat tables. This allows multiple licenses and renewals for a license to all be associated with an individual and the applicant doesn't have to re-enter all of their personal info. When the status of a license application is updated (Approved/Denied/Incomplete/etc.), I want to send the applicant an email with which license (license type, new/renewal) had it's status updated and what the new status is.
In Make, I can see exactly which field values have been updated and the globalID and objectID of the repeat feature they were changed in. That allows me to setup filters on the exact items that have changed, but when I try to make the actual emails, I cannot access fields that weren't updated in a specific repeat table. Make always pulls data from fields in the first repeat feature. Is there a way to access only the edited repeat feature or a way to use the globalID or objectID to specify which feature to pull the fields from?
I did attempt to use "-1" in an array to try to grab the most recently created feature in the repeat table, but that only pulled a value (and threw an error in Make) and didn't specify which item in the array to access.
Accepted Solutions
Okay, I got the results I wanted. I setup the Iterator module pointing at the repeat table array.
I then had to add an AND statement to my filters to have the globalID coming out of the Iterator match the glabalID in the Response -> updateResults.
From there, I needed my emails to pull fields from the Iterator output and not from the Survey outputs because that still pulled data from the first feature in the repeat table.
This seems to be getting the output that I was after, but if there was a more straight forward way of telling Make which feature in the repeat table to grab, I'd love to hear it. This seems pretty clunky since it has the filters rejecting multiple bundles every time.
Yes, the Iterator will break the repeat table apart and run everything downstream of it once for each record, but how do I specify the single record I want it to return? I tried using the map() function in a Set Variable module, but it always returns empty or, when I used it with the iterator, it returned empty multiple times.
Okay, I got the results I wanted. I setup the Iterator module pointing at the repeat table array.
I then had to add an AND statement to my filters to have the globalID coming out of the Iterator match the glabalID in the Response -> updateResults.
From there, I needed my emails to pull fields from the Iterator output and not from the Survey outputs because that still pulled data from the first feature in the repeat table.
This seems to be getting the output that I was after, but if there was a more straight forward way of telling Make which feature in the repeat table to grab, I'd love to hear it. This seems pretty clunky since it has the filters rejecting multiple bundles every time.
