Great suggestion! I have been playing around with several approaches for approval in recent weeks. I always hit a problem when I must consider the situation where the file being approved is modified mid-process. If I want to secure document coherence, I must manage that. The internal approval functions in SP do that with versioning. Is there a way to add that to your solution without using PA?
Thank you for the video!! How do I make sure that approvers only see the item they supposed to approve in the library, in a case where I have multiple items in progress that is being processed by other approvers. Only see what you suppose to approve. Thank you
This is great however i have followed all the steps but Patch is having an error on completed approver,' indicating its expacting a Record and its getting a table"
hi Krishna great suggestions thank you. i looking approval system where we can send approval for multiple members using conditions. need your assistance.
Hi Krishna, Thanks for making a video. this looks cool! just wondering how we are restricting the form for the specific approvers? like first approver is Smith but Krishna is approving. this shouldn't be the case right? is there a way to restrict on app load if it is not the intended approver? otherwise anyone having the link to this approval page can approve even the requestor. Just let me know the event name where we have to write the if logic to check user() with the current approver from datasource
Thank you for reviewing my solution. Here are few recommendations: 1. When you open the Power App in the studio, you can see App in the left nav. You can define your logic for user in onstart property (OR) 2. SharePoint Integration also has properties OnEdit, OnDisplay, OnNew. Based on your requirement, you can define user check in respective properties and Navigate to appropriate screen if the current user does not match with Task Assigned user (OR) 3. On the screen's Onvisible property also you can check and navigate away if the user does not match with Assigned To user.
Hello Krishna, how can the 3 approvers be static and how can each approver add their signatures as it goes through the approval process? In my case all the three approver would be the same for this approval process...finally, can I add the requestors name to automatically be added in the cc field and have a submission acknowledgement? Thank you Sandy (using Hubby's acct). Thank you!!!
If the approvers are static, you can maintain them in a SharePoint list and refer them from the Power App everytime you are assigning a task. Absolutely, you can add requestors name automatically be added in the CC field.
@@KrishnaRachakonda Thank you Krishna! may I humbly ask if they are any tutorial videos that you can recommend that can walk me through it? Thank you for responding! Sandy
Thank you for the great video, but I'm really stuck and need more help 🥺 Is there a way you can export the app or send me just the code because not everything is shown in the video? Thank you in advance!
I get an error immediately varApprovers and it won't show up when I type it. Is the variable defined somewhere else or is it only in the ClearCollect? Thank you for your response
sorry, could not reply in time. code is not in one place as there are multiple components. share your contact tinyurl.com/contactmesk and specify which part of the code you are looking for.
@@KrishnaRachakonda Hey Bud, thanks for the detailed video. I have submitted my email on the above form, could you please send the code when you get a chance? TIA
why reengine the whole power automate function in PowerApps? IF this could be done in flow easily why invest all this? But at least you could provide the code in description why everyone has to ask for the code...Too much unnecessary hassle on top of it I can't even imagine putting all this effort and finding out it doesn't work , at latest if code is was provided it does help to quickly get it done ....but thanks anyways. Pls next time post the available resources /code especially this too long one is pain in ass not everyone is coder like you
Flow has its own limitations - API Call limits, 28 day history, Task management and so on. This video provided an alternate approach. This approach was implemented for a specific use case. You do not have to use this approach if your approval process is simple. I understand your pain with video. This was my oldest video and I do not have code for this anymore. The video was created to share the users that there is an alternate approach but not to share the code. I will make this video private so that no user run into the issues you came across. This application is actively being used by the customer even today. Unfortunately, I cannot access their tenant to get the code. Appreciate your feedback.
