Record owner of record created with QuickBase Actions

I have run into this as well. I think that's the way they programmed initially, and it is not acceptable. Right now the user who set up and saved the Action is going to be the owner of all records created by it. They need to change that with the next release (hopefully).

I agree, but I'm not so sure that Quick Base sees this as a bug or if its on any enhancement list.  One option is to have a dedicated userid for Actions and Webhooks so that the user is a system type userid and not a real person.

I also am not quite sure what happens to a Webhook or Action when the user eventually becomes deactivated.  I have that like by 101st thing to do on my todo list to understand that out of a concern that the Action or Webhook will become disabled.

Yeah, if a consultant or developer like you has temporary access to someone's app, sets up the Action or Webhook, and then goes away and the user is disabled, that is more than a huge annoyance. I think they ought to set it up using application tokens, and you could tie a token to a specific user or flip it to a different user if things change.

Thank you for the replies!

You can use the API_ChangeRecordOwner to trigger  a webhook  that can change the record owner.

This is definitely something that is much needed.  What would be preferable is if you could set the record owner of the new record to either - record owner of trigger record, user from a field, or current user (user that saved the record and fired the web action).  I believe one issue probably stems from the fact that the record owner, like the record ID#, isn't populated until after a record is created.  So if the action is fired as part of the 'saving' process of a new 'triggering' record, there isn't a value to pass.  This comes up in other circumstances as well.  Much needed enhancement, but probably more complicated to implement than it sounds at first.  

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 really hope they can add some functionality to be able to copy over the user that should be the record owner so it is not always the person creating the Action.

You can use the API_ChangeRecordOwner to trigger  a webhook  that can change the record owner.- I use this and it works perfectly

Hello, I'm not sure if I caught all of the above and whether or not it was figured out.  I added a user field to my change log table and it populates with the current user.  The last modified by field is my name but I captured the user that was making the changes. I used a QuickBase action to log the change.