Disallow updating rows more than once

[tinok]

We need to modify the script so that it skips the initial KoBo-to-Airtable submission IF the row already includes a UUID in the Airtable COL submission_uuid field.

Background

The current online survey approach has some users forwarding the survey URL (including the "unique" participant ID) to whole groups of people. This means that:

• There may be multiple KoBo submissions for the same participant ID, each resulting in a new set of referred contacts
• Each successive submission with the same participant ID is resulting in the reward phone number being overwritten

For example:

1. Alex takes survey (respondent ID 1), refers Tino (ID 2).
2. Tino receives survey URL, and forwards it by group message. He also takes the survey, referring John and Ignacio, adding his phone number for rewards (111-222-3333).
3. Anji takes the survey from the URL Tino forwarded in step 2. He refers Patrick and Katrina. He specifies his reward phone number (234-400-5000).

Current behavior:

Tino's phone number is replaced by Anji's. Patrick and Katrina are added as new referrals to the table. There are now 5 records (Alex, Tino, John, Ignacio, Patrick, Katrina). Tino's record says he referred 4 people (John, Ignacio, Patrick, Katrina).

Desired behavior: One of these two options:

1. Patrick and Katrina are not added to Airtable
2. Patrick and Katrina are added but the record updating script DOES NOT update Tino's record (because he already has a UUID in the Airtable COL submission_uuid field). (This would require the team filtering out the additional referrals in Airtable, which is ok.)

[dorey]

In this example, would it work if we check to see if Tino has a referral number set, and if it is set we don't change it? This seems like it would prevent the underlying problem.

And then we could add Patrick and Katrina in and (somehow) mark them as coming from an over-submitted referral link which would make it easier to filter out

[jnm]

@dorey, sounds good to me 👍

I'd guess that this issue is making a bit of a mess in the Airtable, so pushing a fix first for

we check to see if Tino has a referral number set, and if it is set we don't change it

would probably save a lot of labor. The next part

mark them as coming from an over-submitted referral link

is certainly nice, but please don't worry about doing this first. Perhaps, given what @tinok says, it's not needed at all.

[tinok]

That's right, adding Patrick and Katrina is not necessary from their perspective. This was only a suggestion in the first post because we're already adding them.

Once Patrick and Katrina don't have Tino's referral number set anymore we will know that they came from an overcommitted referral and can filter them out as needed.