When the event "A row in table A is created or updated" fires, you have all the data of the created/updated row. Why can't I fire an action to update some columns in a row of different table, when all the data from the record that fired the action could be available as _THISROW and all we would need is a way to filter to rows to be updated on the target table ?
For example lets say I have a LEADS table and a QUOTES table. When I create a QUOTE I may indicate the Lead that quote is linked to, and so I would like to mark the lead as "Quoted" when a quote for that lead is creted. I would expect to accomplish this task using a setup like this:
---- BOT ---
event: Row in QUOTES is added or updated
action: setLeadAsQuoted
--- ACTION --
table: LEADS
action: update columns in a row
set: [STATUS] = "QUOTED"
where: AND([NUMLEAD] = [_THISROW].[NUMLEAD],[STATUS] = "PENDING" )
I know that I could solve this situation creation a bot that apply an action upon a set of rows, but I wonder why the above setup can not be accomplished.
@victorespina wrote:
I wonder why the above setup can not be accomplished.
It's too niche. Can't implement shortcuts for every niche need.
IF the table "Leads" row is referenced in table "Quotes". Then you can follow this video to make the change with automation. Would have either on an add or can add to scheduled to check through these ref keys and see if their look up value for this row <> "Quoted" yet.
When you select the ref key it chooses that row. For any other columns chosen to run in this process those become updated or will change value.
User | Count |
---|---|
18 | |
10 | |
8 | |
6 | |
5 |