I am trying to build an automation where multiple choice preferences of a customer under multiple columns need to be matched with another table where these preferences are mapped to an expert. I am unable to find the output of the right mapping. Can someone help with a workflow direction ?
+28Hey
Would you mind sharing some more detail? I think you’ll really want to take a look at Airtable Deep Matching latest feature as this might help you avoid building an automation altogether?
Having said that, if you still think Automation is the way to go, would you mind sharing a screenshot of your current setup? One of your tables, and one of your actual automation.
Completely different matter, but would love to have you join our Airtable Hackathon! Make sure to sign up!!
Mike, Consultant @ Automatic Nation
YouTube Channel
+2Hello,
Sharing the snapshot below. Its a simple query, but I am not able to get matches for my clients when there are multiple selections done by clients.
Looking forward to getting some help on this.
My expert base is the first snapshot and the client preference is the second snapshot.
Noted on the hackathon !
+28Hey
You’ll want to have:
Trigger (e.g. when a record matches conditions on the Customer Preference table)
Find records on the Expert details table based on condition where: Language has any of {Preferred language}, AND Expertise has any of {Preferred language}.
You’ll then might want to have a junction table for mapping these matches (video on junction tables here), or just link found records from Expert Details table to a field in Customer preference table.
I would HIGHLY suggest you create new tables for Languages and Expertises, and use them as libraries. I believe you’ll find the video below (similar use case for matchmaking) really useful.
If you need any additional help, feel free to grab a slot using this link.
Mike, Consultant @ Automatic Nation
YouTube Channel
+21I just want to chime in and especially echo Mike’s recommendation for a junction table to express the match. I’ve been building out an interpretation ticketing/request system with matchmaking, and I had to re-engineer a substantial amount as I started thinking a junction table wouldn’t be necessary.
+28Oh yes, I would really encourage the use of junction tables for this use case. By having it you could track on a 1:1 basis status of the corresponding introduction between Client and Expert for instance.
Mike, Consultant @ Automatic Nation
YouTube Channel
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.