cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
kilaj1
Resolver I
Resolver I

Strange form submit behavior to SPO list

I've been working on a fairly complex PowerApp for some time.  I'm at the stage now where I'm making approvals, although there may be other ways to do it, I've opted to use a SPO list with PowerApps to control the approvals.

 

In my SPO list I have three columns per approval, One showing the actual Status of the approval (Approved/Not Approved), The Approver (Text field), and Approval Date (date field).

 

On my Approvals Page in PowerApps I have 4 stages to my approvals

kilaj1_0-1629146410642.png

 

On select of the "approval" button on each stage I have a UpdateContext and a submit form. This code snippet is stage 1

 

UpdateContext({FundApproval:"Approved"});
UpdateContext({FundApprovor:User().FullName});
UpdateContext({FundApprovalDate:Today()});

Set(glbStatus,"R Approval");//Next stage of approvals

SubmitForm(MasterForm);
Patch('Master List Form',LookUp('Master List Form',ID = MasterForm.LastSubmit.ID),{},AttachmentsForm.Updates);

 

the Form on this page is tied to a master list (MasterForm) and on submitting it updates SPO.  This has worked in all areas of the PowerApp including the Global Status I have in the screen shot. 

 

The problem is with the Approval status of each stage that use the Update Context.  When I click the button for teh first stage to approve it, the master form gets updated information, i.e. the three "UpdateContext" entries, BUT the data does not get updated in SPO UNTIL click on the approval button for the second stage.  I figured this was some kind of weird delay issue, where in because i have the updatecontext and the submit in the same button, the master form submit code executes before it captures the updatecontext information. And this proven true for the subsequent stages.

 

So I separated the code into another button with just:

 

SubmitForm(MasterForm);
Patch('Master List Form',LookUp('Master List Form',ID = MasterForm.LastSubmit.ID),{},AttachmentsForm.Updates);

 

and sure enough, I click the Approval button, which runs the UpdateContext info and then click the "Submit form" button, and then SPO updates accordingly. 

 

I've seen behavior like this in InfoPath days, and the solution was to add a delay, but I don't see a simple way to do that in Power Apps.  I'm hoping I can find a solution that wouldn't require me to have to buttons to click on for approval (one to approve, one to submit).

7 REPLIES 7
RandyHayes
Super User
Super User

@kilaj1 

In general your problem is coming from the fact that you are immediately in your action formula, patching another list with the results of the Submit.  The evaluation of your formula will not "Wait" at submitform until it is done, it will issue the submit form and then move directly to the Patch statement - meaning, how do you, first of all, know that the form submitted? and second, how do you know the last submit record is complete yet?

 

If the AttachmentsForm is writing the the same record that your MasterForm is, then you should consider moving this all into your form submit instead of making two data calls.  

 

If the Master List Form is a different datasource than the MasterForm datasource, then you should move the following into the OnSuccess of the MasterForm:

Patch('Master List Form',
   LookUp('Master List Form',ID = Self.LastSubmit.ID),
   AttachmentsForm.Updates
);

 

HOWEVER, based on your formula and that you are looking up into a list based on the last form submit ID, then I believe my first observation was correct, and you should really be submitting only 1 form and not trying to patch after.

 

I hope this is helpful for you.

 

_____________________________________________________________________________________
Digging it? - Click on the Thumbs Up below. Solved your problem? - Click on Accept as Solution below. Others seeking the same answers will be happy you did.
NOTE: My normal response times will be Mon to Fri from 1 PM to 10 PM UTC (and lots of other times too!)
Check out my PowerApps Videos too! And, follow me on Twitter @RandyHayes

Really want to show your appreciation? Buy Me A Cup Of Coffee!

Thanks for the reply, I tried moving the patch code to the master list and even tried removing the patch code completely but the behavior remains the same.

 

the strange and not sure if its connected thing is that the global variables don't have an issue with this, just the context ones.

RandyHayes
Super User
Super User

@kilaj1 

So let's dig a little more.  Your suspicion that you need some sort of delay is not an issue, so we'll skip that.

How are you using the context variables in your Form?  What formulas are utilizing them in the form?

_____________________________________________________________________________________
Digging it? - Click on the Thumbs Up below. Solved your problem? - Click on Accept as Solution below. Others seeking the same answers will be happy you did.
NOTE: My normal response times will be Mon to Fri from 1 PM to 10 PM UTC (and lots of other times too!)
Check out my PowerApps Videos too! And, follow me on Twitter @RandyHayes

Really want to show your appreciation? Buy Me A Cup Of Coffee!

hmm now that you ask that question, I'm seriously rethinking how I've actually used them.  but here it is:

A user would save the entire App in draft which I have a global variable for that status, when they get to the approval page they have to click this button to start the workflow approval process, which essentially puts all steps into "not approved" and kicks off a Flow to notify the first group of people.

kilaj1_0-1629205185135.png

this button has the following code

 

Set(glbStatus,"Fundraising Approval");

UpdateContext({FApproval:"Not Approved"});
UpdateContext({FApprovor:""});
UpdateContext({FApprovalDate:Blank()});

UpdateContext({RApproval:"Not Approved"});
UpdateContext({RApprovor:""});
UpdateContext({RApprovorDate:Blank()});

UpdateContext({GApproval:"Not Approved"});
UpdateContext({GApprovor:""});
UpdateContext({GApprovordate:Blank()});

UpdateContext({TApproval:"Not Approved"});
UpdateContext({TApprovor:""});
UpdateContext({TApprovordate:Blank()});

SubmitForm(MasterForm);
Patch('Master List Form',LookUp('Master List Form',ID = MasterForm.LastSubmit.ID),{},AttachmentsForm.Updates);

Notify("Approval Process started successfully", NotificationType.Success);

 

Below that I have a Form control that has 4 stages of approval, this Form is tied to a "Masterform" on a different page.

 

kilaj1_1-1629206795436.png

For F Approval, I added a the button and the Cancel button (circle with the X) to the data card.

Next to that, two fields (cards), one for the Approver and the other for the Approval Date.

 

Approver code:

Default:

 

FApprovor

 

Approval Date code:

Default:

 

FApprovalDate

 

 

For the Blue Button this, is the code

Text

 

FApproval

 

On Select:

 

UpdateContext({FApproval:"Approved"});
UpdateContext({FApprovor:User().FullName});
UpdateContext({FApprovalDate:Today()});

Set(glbStatus,"R Approval");



//SubmitForm(MasterForm);
//Patch('Master List Form',LookUp('Master List Form',ID = MasterForm.LastSubmit.ID),{},AttachmentsForm.Updates);

 

Display mode:

 

If( glbStatus= "F Approval"|| glbStatus = "F Approval Canceled",Edit,Disabled)

 

Visible:

 

If(glbStatus= "Draft",false,true)

 

The Cancel button has the following code:

On Select:

 

UpdateContext({FApproval:"Not Approved"});
UpdateContext({FApprovor:""});
UpdateContext({FApprovalDate:Blank()});

Set(glbStatus,"F Approval Canceled");

SubmitForm(MasterForm);
Patch('Master List Form',LookUp('Master List Form',ID = MasterForm.LastSubmit.ID),{},AttachmentsForm.Updates);

 

RC Approval is virtually the same, with some additional logic to enable the button after "Fapproval" is "approved"

 

Going back to the original issue, when I hit that Approved button for FApproval it doesn't update the SPO list BUT then i hit the Rapproval button, then it updates the FApproval information, BUT the RApproval information doesn't get updated, and it cascades from there.

kilaj1
Resolver I
Resolver I

So im doing some additional testing and it seems like the UpdateContext is not passing through and the first click.

 

I was still a bit stuck on the idea of a delay so i started playing around with the timer control.  I have a button that has the code.

 

UpdateContext({TimerGo: true});

in the timer.start I have  TimerGo

 

when I click the button the timer does not start.  after i submit the form and go back the second time around, the timer works.  this is similar behavior as above, only after the second submit does it take the updatecontext

RandyHayes
Super User
Super User

@kilaj1 

Yeah, the timer is not going to be of any value to you. 

But your formula for the SubmitForm still has the Patch immediately after it.  As I mentioned in message 2, this should be in your OnSuccess action. That is going to cause a problem.

 

The other problem I see is that you mention your form is on another page.  So, if the form is somehow trying to use context variables, that will not work.

 

The real key here is that you shouldn't need any of these variables and what you have should be centered around your form.  No other patches or anything are needed.  The formulas you have are pretty "code-y" and PowerApps is not a coding platform, so let's see what we can do to get you closer to working properly.

 

So let's start with this - I am not seeing the connection of all of these variables to your form.  How is the information you are gathering through the approval stages being stored?  What is the form about, and why do you have two forms?

 

I think if I can start to get to know your app a little better with these forms and variables, I will be able to give you a very specific solution rather than just some guesses.

 

So, let me know.  I have your post flagged in my system so I will stay on top of it with you.

 

I'm about 14 to 15 hours until next response, so feel free to respond and I will get back to you after that time.

 

_____________________________________________________________________________________
Digging it? - Click on the Thumbs Up below. Solved your problem? - Click on Accept as Solution below. Others seeking the same answers will be happy you did.
NOTE: My normal response times will be Mon to Fri from 1 PM to 10 PM UTC (and lots of other times too!)
Check out my PowerApps Videos too! And, follow me on Twitter @RandyHayes

Really want to show your appreciation? Buy Me A Cup Of Coffee!

Thanks again.  Yes I was mainly trying to see how the UpdateContext worked outside of my setup with the timer.  As for the patch in my testing I have it removed just forgot to take it out in my post.

 

The other problem I see is that you mention your form is on another page.  So, if the form is somehow trying to use context variables, that will not work.

 

I'm actually using your suggested method for managing multiple Form Controls in a PowerApp

https://www.youtube.com/watch?v=2E4FXNPLVXw&t

The real key here is that you shouldn't need any of these variables and what you have should be centered around your form.  No other patches or anything are needed.  The formulas you have are pretty "code-y" and PowerApps is not a coding platform, so let's see what we can do to get you closer to working properly.

 

The more I test and look at what I've done I'm inclined to agree, this is me coming from infopath thinking I guess

 

kilaj1_2-1629296292961.png

Using the diagram above, I've stripped the UI down to bare minimum.

In Form7 in my PowerApp, the Item is set to glbCurrentRecord which is on a master Form which has the fields from Form7.

 

Using FApproval stage as the example, the InputFields "Card: AP_Fapproval" has the Default set to FApproval, "Card: AP_FApprover" has the default set to FApprover, and then "Card: AP_FApprovalDate" is set to FApprovalDate. In hindsight this looks pretty wrong considering that it wont show the true value in SPO once you don'thave that variable loaded.

 

Once the initial button "Start Approval Process" is clicked, the cards in Form7 get set based on the Updatecontext mentioned before, basically setting all stages to "Not approved", No approver and no date of approval.

 

When you click on the Approval Button, it updates the fields in Form7

 

Set(glbStatus,"R Approval");
UpdateContext({FApproval:"Approved",FApprovor: User().FullName,FApprovalDate:Today()});
SubmitForm(MasterForm);

 

 and then it would submit the master form and change the global status to "R Approval" which is the next stage.

 

I'm almost thinking of breaking this down into a simple toggle for the approved/not approved.  The addition of the buttons to control the approved/not approved is what lead me down the UpdateContext path.

 

Helpful resources

Announcements

Exclusive LIVE Community Event: Power Apps Copilot Coffee Chat with Copilot Studio Product Team

  It's time for the SECOND Power Apps Copilot Coffee Chat featuring the Copilot Studio product team, which will be held LIVE on April 3, 2024 at 9:30 AM Pacific Daylight Time (PDT).     This is an incredible opportunity to connect with members of the Copilot Studio product team and ask them anything about Copilot Studio. We'll share our special guests with you shortly--but we want to encourage to mark your calendars now because you will not want to miss the conversation.   This live event will give you the unique opportunity to learn more about Copilot Studio plans, where we’ll focus, and get insight into upcoming features. We’re looking forward to hearing from the community, so bring your questions!   TO GET ACCESS TO THIS EXCLUSIVE AMA: Kudo this post to reserve your spot! Reserve your spot now by kudoing this post.  Reservations will be prioritized on when your kudo for the post comes through, so don't wait! Click that "kudo button" today.   Invitations will be sent on April 2nd.Users posting Kudos after April 2nd. at 9AM PDT may not receive an invitation but will be able to view the session online after conclusion of the event. Give your "kudo" today and mark your calendars for April 3rd, 2024 at 9:30 AM PDT and join us for an engaging and informative session!

Tuesday Tip: Unlocking Community Achievements and Earning Badges

TUESDAY TIPS are our way of communicating helpful things we've learned or shared that have helped members of the Community. Whether you're just getting started or you're a seasoned pro, Tuesday Tips will help you know where to go, what to look for, and navigate your way through the ever-growing--and ever-changing--world of the Power Platform Community! We cover basics about the Community, provide a few "insider tips" to make your experience even better, and share best practices gleaned from our most active community members and Super Users.   With so many new Community members joining us each week, we'll also review a few of our "best practices" so you know just "how" the Community works, so make sure to watch the News & Announcements each week for the latest and greatest Tuesday Tips!     THIS WEEK'S TIP: Unlocking Achievements and Earning BadgesAcross the Communities, you'll see badges on users profile that recognize and reward their engagement and contributions. These badges each signify a different achievement--and all of those achievements are available to any Community member! If you're a seasoned pro or just getting started, you too can earn badges for the great work you do. Check out some details on Community badges below--and find out more in the detailed link at the end of the article!       A Diverse Range of Badges to Collect The badges you can earn in the Community cover a wide array of activities, including: Kudos Received: Acknowledges the number of times a user’s post has been appreciated with a “Kudo.”Kudos Given: Highlights the user’s generosity in recognizing others’ contributions.Topics Created: Tracks the number of discussions initiated by a user.Solutions Provided: Celebrates the instances where a user’s response is marked as the correct solution.Reply: Counts the number of times a user has engaged with community discussions.Blog Contributor: Honors those who contribute valuable content and are invited to write for the community blog.       A Community Evolving Together Badges are not only a great way to recognize outstanding contributions of our amazing Community members--they are also a way to continue fostering a collaborative and supportive environment. As you continue to share your knowledge and assist each other these badges serve as a visual representation of your valuable contributions.   Find out more about badges in these Community Support pages in each Community: All About Community Badges - Power Apps CommunityAll About Community Badges - Power Automate CommunityAll About Community Badges - Copilot Studio CommunityAll About Community Badges - Power Pages Community

Tuesday Tips: Powering Up Your Community Profile

TUESDAY TIPS are our way of communicating helpful things we've learned or shared that have helped members of the Community. Whether you're just getting started or you're a seasoned pro, Tuesday Tips will help you know where to go, what to look for, and navigate your way through the ever-growing--and ever-changing--world of the Power Platform Community! We cover basics about the Community, provide a few "insider tips" to make your experience even better, and share best practices gleaned from our most active community members and Super Users.   With so many new Community members joining us each week, we'll also review a few of our "best practices" so you know just "how" the Community works, so make sure to watch the News & Announcements each week for the latest and greatest Tuesday Tips!   This Week's Tip: Power Up Your Profile!  🚀 It's where every Community member gets their start, and it's essential that you keep it updated! Your Community User Profile is how you're able to get messages, post solutions, ask questions--and as you rank up, it's where your badges will appear and how you'll be known when you start blogging in the Community Blog. Your Community User Profile is how the Community knows you--so it's essential that it works the way you need it to! From changing your username to updating contact information, this Knowledge Base Article is your best resource for powering up your profile.     Password Puzzles? No Problem! Find out how to sync your Azure AD password with your community account, ensuring a seamless sign-in. No separate passwords to remember! Job Jumps & Email Swaps Changed jobs? Got a new email? Fear not! You'll find out how to link your shiny new email to your existing community account, keeping your contributions and connections intact. Username Uncertainties Unraveled Picking the perfect username is crucial--and sometimes the original choice you signed up with doesn't fit as well as you may have thought. There's a quick way to request an update here--but remember, your username is your community identity, so choose wisely. "Need Admin Approval" Warning Window? If you see this error message while using the community, don't worry. A simple process will help you get where you need to go. If you still need assistance, find out how to contact your Community Support team. Whatever you're looking for, when it comes to your profile, the Community Account Support Knowledge Base article is your treasure trove of tips as you navigate the nuances of your Community Profile. It’s the ultimate resource for keeping your digital identity in tip-top shape while engaging with the Power Platform Community. So, dive in and power up your profile today!  💪🚀   Community Account Support | Power Apps Community Account Support | Power AutomateCommunity Account Support | Copilot Studio  Community Account Support | Power Pages

Super User of the Month | Chris Piasecki

In our 2nd installment of this new ongoing feature in the Community, we're thrilled to announce that Chris Piasecki is our Super User of the Month for March 2024. If you've been in the Community for a while, we're sure you've seen a comment or marked one of Chris' helpful tips as a solution--he's been a Super User for SEVEN consecutive seasons!       Since authoring his first reply in April 2020 to his most recent achievement organizing the Canadian Power Platform Summit this month, Chris has helped countless Community members with his insights and expertise. In addition to being a Super User, Chris is also a User Group leader, Microsoft MVP, and a featured speaker at the Microsoft Power Platform Conference. His contributions to the new SUIT program, along with his joyous personality and willingness to jump in and help so many members has made Chris a fixture in the Power Platform Community.   When Chris isn't authoring solutions or organizing events, he's actively leading Piasecki Consulting, specializing in solution architecture, integration, DevOps, and more--helping clients discover how to strategize and implement Microsoft's technology platforms. We are grateful for Chris' insightful help in the Community and look forward to even more amazing milestones as he continues to assist so many with his great tips, solutions--always with a smile and a great sense of humor.You can find Chris in the Community and on LinkedIn. Thanks for being such a SUPER user, Chris! 💪🌠

Find Out What Makes Super Users So Super

We know many of you visit the Power Platform Communities to ask questions and receive answers. But do you know that many of our best answers and solutions come from Community members who are super active, helping anyone who needs a little help getting unstuck with Business Applications products? We call these dedicated Community members Super Users because they are the real heroes in the Community, willing to jump in whenever they can to help! Maybe you've encountered them yourself and they've solved some of your biggest questions. Have you ever wondered, "Why?"We interviewed several of our Super Users to understand what drives them to help in the Community--and discover the difference it has made in their lives as well! Take a look in our gallery today: What Motivates a Super User? - Power Platform Community (microsoft.com)

March User Group Update: New Groups and Upcoming Events!

  Welcome to this month’s celebration of our Community User Groups and exciting User Group events. We’re thrilled to introduce some brand-new user groups that have recently joined our vibrant community. Plus, we’ve got a lineup of engaging events you won’t want to miss. Let’s jump right in: New User Groups   Sacramento Power Platform GroupANZ Power Platform COE User GroupPower Platform MongoliaPower Platform User Group OmanPower Platform User Group Delta StateMid Michigan Power Platform Upcoming Events  DUG4MFG - Quarterly Meetup - Microsoft Demand PlanningDate: 19 Mar 2024 | 10:30 AM to 12:30 PM Central America Standard TimeDescription: Dive into the world of manufacturing with a focus on Demand Planning. Learn from industry experts and share your insights. Dynamics User Group HoustonDate: 07 Mar 2024 | 11:00 AM to 01:00 PM Central America Standard TimeDescription: Houston, get ready for an immersive session on Dynamics 365 and the Power Platform. Connect with fellow professionals and expand your knowledge. Reading Dynamics 365 & Power Platform User Group (Q1)Date: 05 Mar 2024 | 06:00 PM to 09:00 PM GMT Standard TimeDescription: Join our virtual meetup for insightful discussions, demos, and community updates. Let’s kick off Q1 with a bang! Leaders, Create Your Events!    Leaders of existing User Groups, don’t forget to create your events within the Community platform. By doing so, you’ll enable us to share them in future posts and newsletters. Let’s spread the word and make these gatherings even more impactful! Stay tuned for more updates, inspiring stories, and collaborative opportunities from and for our Community User Groups.   P.S. Have an event or success story to share? Reach out to us – we’d love to feature you!

Top Solution Authors
Top Kudoed Authors
Users online (5,555)