Forum Discussion
EvanMartinez
Qrew Elite
Hi Ryan,
It is possible to do that with Automations and pass values across records like that. One question I would have first is if there is an action you can take on a customer that would check a checkbox in all of their related records is there a reason why this shouldn't be stored on the customer record and passed down as a lookup field to all the child records via a relationship? This would then require no extra steps and the customer record would become the source of truth for whether that checkbox is checked. You could then limit the access to that field to only those who should be flipped that checkbox, it passes to any table you set up a lookup for and when you want to uncheck that checkbox if it was a mistake or it is time to remove it for your workflow you uncheck that one checkbox and don't have to hunt it down in every table and uncheck it or also set up a web of Automations to uncheck it. This is especially true if you don't want others to uncheck that checkbox in the child records or if that checkbox should also be checked for any new records that are added after it is checked as well as existing records. When there is an override by that having it exist in one place and cascade down can help to simplify the workflow and avoid extra steps. If you want to go the Automation route you can see an example of that below.
If you are looking to trigger something like that I would suggest using an Automation actually. With an Automation you can set it an automation for each table that should be changed and have it trigger to only change records that have the same Related Customer value. You would just want to match the Related Customer (In my example related company) in your triggering record to the Related Customer in your other tables so you target only the right records for change. Then you can set that checkbox field to be checked as well in the other records. You would just need one for every table that contains a record with that checkbox field. I have included some screenshot examples below and I hope these suggestions are helpful.
------------------------------
Evan Martinez
------------------------------
It is possible to do that with Automations and pass values across records like that. One question I would have first is if there is an action you can take on a customer that would check a checkbox in all of their related records is there a reason why this shouldn't be stored on the customer record and passed down as a lookup field to all the child records via a relationship? This would then require no extra steps and the customer record would become the source of truth for whether that checkbox is checked. You could then limit the access to that field to only those who should be flipped that checkbox, it passes to any table you set up a lookup for and when you want to uncheck that checkbox if it was a mistake or it is time to remove it for your workflow you uncheck that one checkbox and don't have to hunt it down in every table and uncheck it or also set up a web of Automations to uncheck it. This is especially true if you don't want others to uncheck that checkbox in the child records or if that checkbox should also be checked for any new records that are added after it is checked as well as existing records. When there is an override by that having it exist in one place and cascade down can help to simplify the workflow and avoid extra steps. If you want to go the Automation route you can see an example of that below.
If you are looking to trigger something like that I would suggest using an Automation actually. With an Automation you can set it an automation for each table that should be changed and have it trigger to only change records that have the same Related Customer value. You would just want to match the Related Customer (In my example related company) in your triggering record to the Related Customer in your other tables so you target only the right records for change. Then you can set that checkbox field to be checked as well in the other records. You would just need one for every table that contains a record with that checkbox field. I have included some screenshot examples below and I hope these suggestions are helpful.
------------------------------
Evan Martinez
------------------------------
RyanSherman1
5 years agoQrew Member
Evan!!!!
Thank you so much!! the automation worked perfectly! I appreciate you!
Thanks again!!
------------------------------
Ryan Sherman
------------------------------
Thank you so much!! the automation worked perfectly! I appreciate you!
Thanks again!!
------------------------------
Ryan Sherman
------------------------------
- RyanSherman15 years agoQrew MemberEvan, thank you for your help thus far; I was able to set up the automation to populate the other table, however I am going in circles with the following issue.
I have set up the automation to feed the check box column into the original table. So table A once the box "script Check" is checked it moves into the second table for employee number 2 to complete a script check on the customer. Employee 2 does a check, and then clicks "Script on File" which then auto populates that field on the original table.
The problem is that its autopopulating that entire column, meaning every customer is getting auto populated when the automation runs from Table 2 back to the original table? Any ideas how to get around this?
------------------------------
Ryan Sherman
------------------------------- EvanMartinez5 years agoQrew EliteHi Ryan,
If you are triggering another Automation are you making sure that the related customer is being drawn in for every automation? That related customer would mean it should only find and check the box on other records that are for the exact same customer. Though it does mean it would check the box on every record with the exact same customer. Otherwise you would need to build another filter into your automation to target only the exact right records. The Automations need to have filters built in to help them target the right records.
------------------------------
Evan Martinez
Community Marketing Manager
Quick Base
------------------------------