Forum Discussion
MarkShnier__You
Qrew Legend
6 years agoI think that you would be better served by having a user field for [ Assigned to]. You can default it to the current user, but when Auto Created by an Automation you will be able to populate it with the [Last Modified by] of Automation triggering record.
I don't think that you can modify the [Record Owner]
------------------------------
Mark Shnier (YQC)
Quick Base Solution Provider
Your Quick Base Coach
http://QuickBaseCoach.com
markshnier2@gmail.com
------------------------------
I don't think that you can modify the [Record Owner]
------------------------------
Mark Shnier (YQC)
Quick Base Solution Provider
Your Quick Base Coach
http://QuickBaseCoach.com
markshnier2@gmail.com
------------------------------
- IvanWeiss6 years agoQrew CaptainI do have Assigned To as another field. I have notifications set for whoever creates the task so they get updates. Because the automation defaults to me, I get all the notifications. Not the user that created the task. This button creates 12 tasks so I was trying to avoid using a rich text button with code. Easier to manage with automation. But I cant have the task originate from me as the developer.
------------------------------
Ivan Weiss
------------------------------- MarkShnier__You6 years ago
Qrew Legend
Then I suggest you create a User field called [Who to Notify} and use that in your Notifications.
------------------------------
Mark Shnier (YQC)
Quick Base Solution Provider
Your Quick Base Coach
http://QuickBaseCoach.com
markshnier2@gmail.com
------------------------------- IvanWeiss6 years agoQrew Captain
But how would the automation populate that? I have a field like that as a list user formula field with the record owner, assigned to field, and a list user field of additional followers.
the automation needs to assign the sending user as one of these notifiers
------------------------------
Ivan Weiss
------------------------------