I have a bot set up that is supposed to record in a ‘Remarks’ column when an item is reassigned from one person to another. The bot triggers on an data change event and the associated action is as below:
First off I receive an error in the expression when trying to set the value in the column under the action itself, however when I check the action settings in the bot, I do not get the expression error.
Secondly, this just records in the Remarks column the [Tech] info after it was saved.
Does an action flow not have the availability to access [_THISROW_BEFORE] and [_THISROW_AFTER]? Can this only be accomplished through reports and templates? Does anyone have a workaround for this?
Thank you.
1 Like
I have to rely on experts on the question of the availability of before&after field values outside templates.
I can propose a not so pretty workaround if you would be interested based on bunch of actions.
- Create a temporary col to hold a next assignee
- Create a form to capture user input in the Next Assignee
- Create an action (APP: Go to another view within this app) to open the form 2) using LINKTOROW
- Create an action to update the Remarks column using the assignee and the next assignee cols (what you have in your CONCATENATION)
- Create an action to copy the value from the next assignee to the current assignee
- Create an action sequence to to do 4) and 5)
- In Behavior >> Event Action of the Form 2), set the action sequence 6)
You need a bunch of house cleaning to hide unnecessary action buttons (and some Form fields) but only show 3) to initiate a new assignment.
Hope this will be useful..
1 Like
Hi @Markus_Malessa , You seem to be concatenating the previous contents of the [Remarks] column. This means previous assigned to is available in the concatenated column. In such a case, may we know any specific reason that you cannot simply use "CONCATENATE([Remarks], "Reassigned to " , [Tech], " on ",TODAY())
1 Like
@Suvrutt_Gurjar
You gave me another idea. Perhaps the Remarks col can be parsed to retrieve the previously assigned tech to construct a new string. It maybe tough/clumsy without Regex though.
1 Like
Yes , correct @TeeSee1 , that is also worth trying. But I believe it does not serve much purpose of parsing again just for immediate next statement because the earlier value is anyway available close by, unless I am missing some point.
A similar requirement post thread below
https://www.googlecloudcommunity.com/gc/AppSheet-Q-A/User-Change-Audit-Trail/td-p/226324