Oct 24, 2023 09:23 PM - edited Oct 24, 2023 09:27 PM
Hi there!
I've created and automation that does the following when a record getting updated...
Here's where I need support figuring the next part out...
Once the above automation runs and I then update 1 record in FIELD A the automation will still run but only tweaking that 1 record accordingly...
What I need it to do is rescan all 50 records and adjust FIELD F, FIELD E, FIELD G based on the edits.
So in the attached example if I change record 1 (Test 6) to (Test 5) the automation will update record 1 to add the values from records 5 ...
Record 1 - Value1_Group to CAT and BIRD (added BIRD)
Record 1 - Value2_Group to 0001 and 0005 (added 005)
Record 1 - Value3_Group to Skates (no change)
I also want it to also rescan all the records and update accordingly so in this case records 5 would get the new record 1 group values
Record 5 - Value1_Group to CAT and BIRD (added CAT)
Record 5 - Value2_Group to 0001 and 0005 (added 001)
Record 5 - Value3_Group to Skates (added Skates)
Screenshots of first bulk record update and 2nd with only record 1 update for demo purposes.
Oct 24, 2023 09:56 PM
Hello! This seems like a fairly simple solution by splitting into two tables and using the "Link to another record" field. One table for collecting data entries. Another table for displaying the collected data utilizing the "Look Up" or "Roll Up" field types. This should in theory do exactly what you're looking for without automations.
This would then also not have a trigger point for summing up the data. If you're looking to have more control over the trigger point, I'm sure there are additional steps we could add.
Let me know if you want me to go into further detail on the two tables 🙂
Oct 25, 2023 10:21 PM - edited Oct 25, 2023 10:28 PM
Hi there!
Thanks for the response. After thinking through your comment I looked around and engineered a solution but am stuck on one part and wondering if it's even possible.
Table 23 - is the data.
Table 23 copy - is the duplication checker
Oct 25, 2023 10:46 PM
Ah yes. So I think what I mean is actually to have one Table 23 as a data collector, and then Table 24 as the data display. It does mean that the data in Table 23 is a bit messy, but that shouldn't matter too much.
I've made a template for you to check out. Again, I'm not sure if this is the solution you're looking for.
https://www.airtable.com/universe/expUbopxZfVlKeAJm/for-chrisberry