Form submitted - assigned a certific

Is their email the primary field in that table?  If it is not that is why since it is technically trying to create a new record by placing the email in that field.

No, it’s actually attempting to use the record ID, or rather that’s what I was attempting run through it.  I’ve tried different options.

The primary field was a fx, but I changed it to a text field.

As you see, I did change the first field to an email field, but there’s no email listed as the find records is looking into the second table to find the certificate # to assign to the person filling out the form(attached to the 1st table).

From your screenshots I do not see recordId anywhere and the configuration is a little confusing the way you explain it.  But you are giving partial images so I cannot see the full configuration and steps.  Also, using views is not the best method for automation triggering. 

Unless you need multiple condition groups I would just tell the Find records to search the certificate table for any unassigned certificate plus any other parameter you need to match to which unassigned certificate, then insert the triggering records recordId into that unassigned certificates User/Assignment field.

There’s recordids above in the find records block, far right.

Not that confusing really.  You have a form filled out, that data is in table 1,

Table 2 has the stored certificate numbers in them.  

Once the form is filled out and received, the automation is triggered(when form is submitted)

Find records looks for the certificate number in the specified view, which has them in order so that the automation doesn’t randomly assign certificates.  It also updates that certificate to assigned, and is removed from the view.  **Key note to your views aren’t the best, AT always suggest that, FYI***
The problem is I’m getting the error, as explained above.
 

Ok.  I worked at Airtable and that is not what we learned thoroughly testing the product but Airtable is more of a sales company so take what they say with a grain of salt.

Good luck!

• Create a View that filters records to show only unassigned certificates.
• Apply sorting in that View to get your desired sequence.
   
• Choose Find records based on "View". The Find Records step will then use the sorted View accordingly.
   

However, the find part isn’t working.  This is from AT :) 

On a basic level, your problem is that you’re feeding a list of multiple Airtable IDs into the Update Record action without wrapping it in a repeating group function. When automations see multiple IDs in the Record ID field unless it’s in a repeating group it doesn’t know which Record you actually want to modify. If your Find Record action resulted on a list of 1 record, then it would work, but you third to last screenshot shows multiple RecordIDs coming through. 

I did finally realize DOH the multi feed into a single field, was part of the problem, however, now I’m getting the above error.  ALMOST THERE!

I think the permissions problem relates to the fact that the BLANK Certificate Recipients table’s primary field is a formula. The automation can’t create new records with the email information (because it’s a formula field) and I suspect the primary field (“Name”) isn’t exactly the same as “Your Email” so it doesn’t know to associate a record instead of creating one. 

I changed the field to a text field.  

i tried it also with an email format for the main field, neither worked.

So part of the issue is in my first table where the form populates the data, my “KEY” field, is a function.  SO I changed that to an email field type, and made sure the email request of the form is tied to that field...That solved.  Since I was updating the linked field in Table 2, it apparently still “sees” the fx field, even though that’s not what I was updating with, oye.

Ok, now new problem, it runs, but it’s assigning the submitted form to ALL the certificate numbers.

If my post about using the email field helped please Like and mark as Solved.

Next problem It is not a new problem, it's the same one I tried pointing out earlier about not using a view but conditions for the find record step and then setting your conditions to find the one certificate.  A couple of ways to do this, one is to restrict the length to 1 when inserting it into the original record so it only grabs one recordId from the list.

Sorry, Garebear, but I’m getting some conflicting answers from both you, others and Airtable.  This is when I’d like to shoot myself.

I’m being told, I don’t have to do the find records!  AGH!

Yeah, this one refuses to work.  I’m just going to have to table it even though it’s 911.