cancel
Showing results for 
Search instead for 
Did you mean: 
Reply

Patch error when resubmitting form with a single control - even though the control is in view mode if the user returns to the form

I am setting a variable "varPrimaryThematicGoal" using the OnSelect property of a radio control: Set(varPrimaryThematicGoal,rdoPrimaryThematicGoal.Selected.Value). I use it to show/ hide cards on subsequent screens. I need to allow users to navigate back to the screen with the radio control, but to prevent them from changing the answer am using this formula on the radio control DisplayMode: If(varPrimaryThematicGoal<>Blank(),DisplayMode.View, DisplayMode.Edit). 

 

My problem is that when someone navigated back to the screen with the radio control and then to another screen, they see a patch error, even though they did not change the selection. 

 

I was getting the same error if they changed the selection and I was hoping that disabling the ability to do so would fix the issue, but no such luck. 

 

I also tried setting the variable when the form is submitted (rather than when the radio is selected) but still seeing the same issue. 

 

Can anyone advise me on what may be happening and how to prevent it? This has me stumped, but I'm a newbie so I must be missing something. Thanks in advance!!!!

17 REPLIES 17
KeithAtherton
Most Valuable Professional
Most Valuable Professional

Hi @KBeale,

 

How is the Patch() function called please?


If I have answered your question, please mark your post as Solved.
If you like my response, please give it a Thumbs Up.
Follow me online.

That’s the weird thing that I should have mentioned, I’m not using a patch function. The error is triggered just by resubmitting the form…

KeithAtherton
Most Valuable Professional
Most Valuable Professional

Thanks for the info. Try changing your code similar to the following - if the variable is not-blank, submit the form then reset the variable (to avoid the SubmitForm() function being called again after navigation):

If(!IsBlank(varPrimaryThematicGoal),
  SubmitForm(frmForm);
  Set(varPrimaryThematicGoal, Blank());
);

If I have answered your question, please mark your post as Solved.
If you like my response, please give it a Thumbs Up.
Follow me online.

I should use the formula you suggested on  OnSelect for the button to submit the form and leave OnSelect for the radio control as: Set(varPrimaryThematicGoal,rdoPrimaryThematicGoal.Selected.Value)? or use it on the OnSelect for the radio control and submit the form from the button using SubmitForm()? Sorry, I’ve tried so many variations I’m getting lost. Thank you so much for your help! I ran out to run an errand and I’ll try what you suggest as soon as I get back! 

KeithAtherton
Most Valuable Professional
Most Valuable Professional

Good question: Use my code snippet in the last message on your form submit button OnSelect property, and keep your rdoPrimaryThematicGoal OnSelect property code as-is (i.e. setting the varPrimaryThematicGoal variable).

 

The thinking behind this is that when you change the radio button selection, the variable is set (which you've done already). When you then submit the form, the variable has a value so the form is submitted then the variable is cleared so clicking the button again will not attempt to submit the form again (and, hopefully, avoid the Patch error).


If I have answered your question, please mark your post as Solved.
If you like my response, please give it a Thumbs Up.
Follow me online.

I tried your code and I was still getting the patch error  😞 I realized that maybe the variable I had set for the rdo value was competing with the global variable I have been using to view the same record across multiple forms (varRecord). I tried using varRecord.'Primary Thematic Goal'.Value="name of choice in rdo Primary Thematic Goal", but when I did, I noticed that value for that column was not updating in the variable when I submitted the form. I added a text label to show varRecord.'Primary Thematic Goal'.Value, and can see that it stays blank, despite the column in the list being updated. Do you have any insight on what could be going on? I am leaning towards just setting the visibilty of cards on subsequent screens with rdoPrimaryThematicGoal.Selected.Value="name of choice in rdo Primary Thematic Goal", but I'm worried it will slow things down pulling from a control a different screen.... And I'm just weirded out that the rdo control selection isn't updating my global variable! Could I be doing something wrong with the rdo control itself? Or could there be an issue with the column? I checked and I do not have column validation turned on, and the column is set to single select and radio buttons in SP. Thanks again for any insight! 

Out of interest, what is the patch error message?

 

Also, the radio control does have an OnChange action property - have you tried using code on this property instead of the OnSelect property?

 

Referencing a control on another screen isn't an ideal practice but worth a test to see if it helps.


If I have answered your question, please mark your post as Solved.
If you like my response, please give it a Thumbs Up.
Follow me online.

The error was saying a conflict with info on the server. When I select an option in the radio control I can still see that the variable is not updating (also when I hit save and submit the form)´. Referencing the control does seem to be working, but I am still stumped as to why the variable isn't updating, as I would prefer to use it. OnChange (and OnSelect) for the radio control are both currently empty (I was relying on adding the value and submitting the form - which IS updating the list). Is there something I shouldf try in OnChange to update update the column value in the varRecord variable (without causing errors ;)). Thanks again for your time! 

Screenshot 2023-04-28 111151.png

KeithAtherton
Most Valuable Professional
Most Valuable Professional

Try setting the radio control OnChange property to set varRecord (or another variable) to see if a variable is updated then the radio control value is changed.

 

Another test would be to call the Patch() function instead of the SubmitForm() function to see if it helps.


If I have answered your question, please mark your post as Solved.
If you like my response, please give it a Thumbs Up.
Follow me online.

Helpful resources

Announcements

Community will be READ ONLY July 16th, 5p PDT -July 22nd

Dear Community Members,   We'd like to let you know of an upcoming change to the community platform: starting July 16th, the platform will transition to a READ ONLY mode until July 22nd.   During this period, members will not be able to Kudo, Comment, or Reply to any posts.   On July 22nd, please be on the lookout for a message sent to the email address registered on your community profile. This email is crucial as it will contain your unique code and link to register for the new platform encompassing all of the communities.   What to Expect in the New Community: A more unified experience where all products, including Power Apps, Power Automate, Copilot Studio, and Power Pages, will be accessible from one community.Community Blogs that you can syndicate and link to for automatic updates. We appreciate your understanding and cooperation during this transition. Stay tuned for the exciting new features and a seamless community experience ahead!

Summer of Solutions | Week 4 Results | Winners will be posted on July 24th

We are excited to announce the Summer of Solutions Challenge!   This challenge is kicking off on Monday, June 17th and will run for (4) weeks.  The challenge is open to all Power Platform (Power Apps, Power Automate, Copilot Studio & Power Pages) community members. We invite you to participate in a quest to provide solutions in the Forums to as many questions as you can. Answers can be provided in all the communities.    Entry Period: This Challenge will consist of four weekly Entry Periods as follows (each an “Entry Period”)   - 12:00 a.m. PT on June 17, 2024 – 11:59 p.m. PT on June 23, 2024 - 12:00 a.m. PT on June 24, 2024 – 11:59 p.m. PT on June 30, 2024 - 12:00 a.m. PT on July 1, 2024 – 11:59 p.m. PT on July 7, 2024 - 12:00 a.m. PT on July 8, 2024 – 11:59 p.m. PT on July 14, 2024   Entries will be eligible for the Entry Period in which they are received and will not carryover to subsequent weekly entry periods.  You must enter into each weekly Entry Period separately.   How to Enter: We invite you to participate in a quest to provide "Accepted Solutions" to as many questions as you can. Answers can be provided in all the communities. Users must provide a solution which can be an “Accepted Solution” in the Forums in all of the communities and there are no limits to the number of “Accepted Solutions” that a member can provide for entries in this challenge, but each entry must be substantially unique and different.    Winner Selection and Prizes: At the end of each week, we will list the top ten (10) Community users which will consist of: 5 Community Members & 5 Super Users and they will advance to the final drawing. We will post each week in the News & Announcements the top 10 Solution providers.  At the end of the challenge, we will add all of the top 10 weekly names and enter them into a random drawing.  Then we will randomly select ten (10) winners (5 Community Members & 5 Super Users) from among all eligible entrants received across all weekly Entry Periods to receive the prize listed below. If a winner declines, we will draw again at random for the next winner.  A user will only be able to win once overall. If they are drawn multiple times, another user will be drawn at random.  Individuals will be contacted before the announcement with the opportunity to claim or deny the prize.  Once all of the winners have been notified, we will post in the News & Announcements of each community with the list of winners.   Each winner will receive one (1) Pass to the Power Platform Conference in Las Vegas, Sep. 18-20, 2024 ($1800 value). NOTE: Prize is for conference attendance only and any other costs such as airfare, lodging, transportation, and food are the sole responsibility of the winner. Tickets are not transferable to any other party or to next year’s event.   ** PLEASE SEE THE ATTACHED RULES for this CHALLENGE**   Week 1 Results: Congratulations to the Week 1 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge. Community MembersNumber of SolutionsSuper UsersNumber of Solutions @anandm08  23 @WarrenBelz  31 @DBO_DV  10 @Amik  19 AmínAA 6 @mmbr1606  12 @rzuber  4 @happyume  7 @Giraldoj  3@ANB 6 (tie)   @SpongYe  6 (tie)     Week 2 Results: Congratulations to the Week 2 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge. Community MembersSolutionsSuper UsersSolutions @anandm08  10@WarrenBelz 25 @DBO_DV  6@mmbr1606 14 @AmínAA 4 @Amik  12 @royg  3 @ANB  10 @AllanDeCastro  2 @SunilPashikanti  5 @Michaelfp  2 @FLMike  5 @eduardo_izzo  2   Meekou 2   @rzuber  2   @Velegandla  2     @PowerPlatform-P  2   @Micaiah  2     Week 3 Results: Congratulations to the Week 3 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge.   Week 3:Community MembersSolutionsSuper UsersSolutionsPower Apps anandm0861WarrenBelz86DBO_DV25Amik66Michaelfp13mmbr160647Giraldoj13FLMike31AmínAA13SpongYe27     Week 4 Results: Congratulations to the Week 4 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge.   Week 4:Community MembersSolutionsSuper UsersSolutionsPower Apps DBO-DV21WarranBelz26Giraldoj7mmbr160618Muzammmil_0695067Amik14samfawzi_acml6FLMike12tzuber6ANB8   SunilPashikanti8

Check Out | 2024 Release Wave 2 Plans for Microsoft Dynamics 365 and Microsoft Power Platform

On July 16, 2024, we published the 2024 release wave 2 plans for Microsoft Dynamics 365 and Microsoft Power Platform. These plans are a compilation of the new capabilities planned to be released between October 2024 to March 2025. This release introduces a wealth of new features designed to enhance customer understanding and improve overall user experience, showcasing our dedication to driving digital transformation for our customers and partners.    The upcoming wave is centered around utilizing advanced AI and Microsoft Copilot technologies to enhance user productivity and streamline operations across diverse business applications. These enhancements include intelligent automation, AI-powered insights, and immersive user experiences that are designed to break down barriers between data, insights, and individuals. Watch a summary of the release highlights.    Discover the latest features that empower organizations to operate more efficiently and adaptively. From AI-driven sales insights and customer service enhancements to predictive analytics in supply chain management and autonomous financial processes, the new capabilities enable businesses to proactively address challenges and capitalize on opportunities.    

Updates to Transitions in the Power Platform Communities

We're embarking on a journey to enhance your experience by transitioning to a new community platform. Our team has been diligently working to create a fresh community site, leveraging the very Dynamics 365 and Power Platform tools our community advocates for.  We started this journey with transitioning Copilot Studio forums and blogs in June. The move marks the beginning of a new chapter, and we're eager for you to be a part of it. The rest of the Power Platform product sites will be moving over this summer.   Stay tuned for more updates as we get closer to the launch. We can't wait to welcome you to our new community space, designed with you in mind. Let's connect, learn, and grow together.   Here's to new beginnings and endless possibilities!   If you have any questions, observations or concerns throughout this process please go to https://aka.ms/PPCommSupport.   To stay up to date on the latest details of this migration and other important Community updates subscribe to our News and Announcements forums: Copilot Studio, Power Apps, Power Automate, Power Pages