Forum Discussion
Is the issue that you're not able to copy the app this way, or that you're trying to do something with the new app and the usertoken isn't valid for the new app that you just created?
If it's some version of the latter - you're best bet is to do an API_Authenticate Request in the Pipeline, get the ticket from the response and pass that ticket into the request as opposed to using the User Token.
------------------------------
Chayce Duncan
------------------------------
I'm just not able to copy the app this way by authenticating with a user account via Pipeline instead of using a user token. The only way it works in Pipeline's is if I change the Make Request connection from user account to user token, and grant that user token access to the app I want to copy.
It just doesn't make sense since my user account is a super user, and I can go to that app right now any copy it.
------------------------------
Jordan Bardwell
------------------------------
- ChayceDuncan12 months agoQrew Captain
Ah - now I see what you're saying. The User Account piece was only rolled out recently (likely the 10th of this month) so it seems that it might be a bug with Pipelines and that type of API call. Best suggestion is give it to QB support to investigate since as you said it's not a security / permissions issue per say.
------------------------------
Chayce Duncan
------------------------------