Forum Discussion
BrianSeymour2
7 years agoQrew Trainee
Yeah, I agree I would be very nice to have the logged in user who triggers the Quick Base action to be the Record Owner of any new records created via the action.
I found a hack that suits our needs after playing with several scenarios including an undocumented (or poorly documented) %curUser% marker, formula fields, additional actions or webhooks, etc. Instead of messing with all that, I opted for simplicity.
Basically, in the "What values will the new record have?" section at the bottom of the Quick Base action "Copy the value from" the "Last Modified By" field in the record that triggers the action and to set a User field in the record that will be created. Then, base reports of this User field instead of the Record Owner field.
In your case you would use the "Record Owner" instead of "Last Modified By" to set the User field.
This is does not achieve exactly what your after, but may be a decent workaround!
I found a hack that suits our needs after playing with several scenarios including an undocumented (or poorly documented) %curUser% marker, formula fields, additional actions or webhooks, etc. Instead of messing with all that, I opted for simplicity.
Basically, in the "What values will the new record have?" section at the bottom of the Quick Base action "Copy the value from" the "Last Modified By" field in the record that triggers the action and to set a User field in the record that will be created. Then, base reports of this User field instead of the Record Owner field.
In your case you would use the "Record Owner" instead of "Last Modified By" to set the User field.
This is does not achieve exactly what your after, but may be a decent workaround!
- DrewVoge7 years agoQrew CadetI use this route now as a workaround, although with some caveats. There are a couple of reasons why you'd want the action to impersonate a specific user. One of them is text fields that log edits. I have a number of quickbase actions that pass text to a text field that logs changes. The 'user' that it shows editing the text is me since the webhook is executed under my credentials. I could always set up these text fields as child records and change 'edits' to new records, but for a lot of situations it's far more complication than is needed. My Q&D fix is to add the users name as text to the beginning of the text string that is being passed, which isn't pretty but works. Small thing though at the end of the day.