Save the date! Join us on October 16 for our Product Ops launch event. Register here.
Jul 08, 2023 12:25 PM
Hi,
I have the following challenge where I would ask for your support:
To give an example - see screenshot of such a transaction:
Defining these rules would work within an automation. Unfortunately they are limited to 50 per base; and I will have more than 50 rules...
I also tried to make a separate rules_table, where each line is a rule and has 3 columns; 1) Stringpart to search for in "TAC-Source" 2) Stringpart to search for in "TAC-Description" 3) the corresponding type value.
Defining the rules would work; but I have no idea how to get them applied, i.e. how to get airtable to check the matching criteria then from the ruleset table to the TACS table.
Anyone with an idea to help? Thank you!!
br Chris
Jul 09, 2023 06:22 PM - edited Jul 09, 2023 06:27 PM
Hi there!
I don't know if this is the most straight forward way to deal with your problem here, but from the info of the post and what I can be bold to assume, I'd suggest the following (without using Scripts)
Idea 1.
I'm not sure if you process the transaction information before it's inputted into your airtable base, however the TAG Description structure looks like it could be split/processed into different columns. By the looks of it what composes the Description is maybe "Item (prescription according to G Translate)" | "MM/YYYY" | Id | Other Items. If possible I would try and process the information previous to entering into Airtable.
Another aspect would be doing the alternative rule table you mentioned with the growing combination of Source & Description and given Ruleset_Match_Type. If you one require the TAC Source and the ID of the Description then it could look something like this. Whenever you would look to add rules, this could be done through a form or directly in the table
If you were able to split the data into separate fields, specially the id value (0704), in theory you would be able to do one simple automation to get the Ruleset_Match_Type from a separate table. The automation would consist on a
Idea 2. (less tidy and scalable)
You could potentially reduce the amount Automations you need for this, without making any changes to the originally data. This would only work would if you have a small/medium amount of TAC Source & TAC Description possible combinations.
You could create views for either category. I'll use Description ID as an example. In each view, you could filter out the TAC Source contains "0704" or whatever Id you've designated that View to.
Once you've done the x amount of View for all your Id's. You can head to Automations and create an Automation that would look something like this per Id. (Shown in pictures below)
This all has assumptions from my side, but hopefully it is somewhat useful. If you need any clarifications on my response I've got no problem following up! Best of luck
Jul 10, 2023 02:21 AM
Hi @Manuel_Tanco Wow - thank you so much for this extensive answer and ideas! Especially the idea with the view is something I absolutely did not have in mind. What I now did, based on your inputs:
This means for each view I started with 1x find and 1x update.
Any further ideas/help on this? thank you! best regards, Chris
Jul 10, 2023 06:53 AM
Always happy to provide possible input!
I've gone through what you mentioned and I don't see a direct scalable way of setting this up due to the trigger option selected, that is without using Scripts for which I can be of little help for this scenario😓. However, maybe the following questions might help
Jul 11, 2023 11:47 AM
Hi @Manuel_Tanco finally I used your views proposal and combined it with a script. Took a while, as my scripting knowledge is very basic, but it works now. Thanks again for your inputs!