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

Custom Dialog to Set Status Value

I have a SharePoint list that is used to collect support requests. I have created a custom PowerApps form and am trying to add a custom dialog that pops up when the "Submission Status" selected value is "Draft". The pop-up opens and informs the user that their request is still in Draft status and asks if they want to Submit it now or save it as a draft. I added two buttons, one for Submit and one for Save as Draft. When they click "Submit", I need the Submission Status value to change to "Submitted". The only two options are "Draft" and "Submitted". If they click "Save as Draft" it just saves the form and closes. The "Save as Draft" is no problem. I can't get the "Submit" button to set the "Submission Status" value to "Submitted". 

Here are the formulas I have used so far:
Custom Save button OnSelect on main form

 

 

If(
SubmissionStatusValue.Selected.Value = "Draft", 
UpdateContext({showDialog:true}),  
SubmitForm(SharePointForm1))

 

 

If the selected submission status is "Draft", set the variable showDialog to True, otherwise submit the form.

Submit button OnSelect in dialog group

 

 

UpdateContext({varSubmissionStatus: "Submitted"});
UpdateContext({showDialog: false});
SubmitForm(SharePointForm1);

 

 

Set the variable varSubmissionStatus to "Submitted", set the variable showDialog to false and submit the form. 

 

grpShowDialog (consists of all elements in the pop-up dialog) Visible parameter

 

 

showDialog

 

 

 

SubmissionStatusValue ComboBox DefaultSelectedItems parameter

 

 

If(
SharePointForm1.Mode = FormMode.New, 
LookUp(Choices('M&D SharePoint Support Requests'.'Submission Status'), Value = "Draft"), If(
showDialog,  
LookUp(Choices('M&D SharePoint Support Requests'.'Submission Status'), Value = varSubmissionStatus), 
Parent.Default))

 

 

If form mode is new, set the default Submission Status value to Draft. Otherwise, if the showDialog variable is true, set the default Submissions Status value to the value of varSubmissionStatus which should have been set to "Submitted" if the Submit dialog button was clicked. Otherwise, set the default to the parent default. 

This does not work. The Submission Status remains "Draft". 

 

Any ideas what I'm doing wrong?

 

7 REPLIES 7

@CCJones 

The default property on a ComboBox is not constantly evaluated throughout the app, it will evaluate it once when the screen is loaded and that is it. to update it, so you cant use things like If statements in that property but you are close to the answer. 

 

Set the Default property of the dropdown to varSubmissionStatus 


Move your If statement to the onStart or onVisible Property, and instead of modifying the default property, you modify the variable. eg. if form new, set variable to draft, if not new, lookup parent value. 


then your submit button essentially stays the same where you update the variable to submitted 

the difference doing it this way is the Default property is just set to the value of the variable and not evaluating an IF statement, so when the variable updates, it triggers the default property to change. 

 

 

Thanks for the response. I tried your suggestion but the Default field won't accept the "varSubmissionStatus" variable because it contains text and not a record. I get an error that it is expecting a record. I can't use a record value primarily because the selected value from the "SubmissionStatusValue" combobox is what I need to check and update if the user chooses the "Submit" button on the pop-up dialog. In the form, I am using the UpdateContext function to make changes to the variables (varSubmissionStatus and showDialog). You had mentioned using the OnVisible property of the form to set variables, but it won't let me use UpdateContext there. I tried using Set, but that didn't work.

This is all so ridiculously complicated. I never had this kind of trouble when I was using Nintex for building solutions. Our company went to SP Online and dumped Nintex, so I'm stuck with the Power Platform. Not being a developer makes it a lot more difficult for me. I feel like I'm so close to having it, but I just can't figure out the final bit which is populating the "SubmissionStatusValue" combobox with "Submitted" and saving that value if they click the "Submit" button. All my other controls work as expected. The pop-up opens if "SubmissionStatusValue.Selected.Value = "Draft". It saves as "Draft" if the user clicks the "Save as Draft" button because nothing has to be done but submit the form.  It's just this pop-up dialog "Submit" button that is giving me nothing but headaches. 

I've changed all the UpdateContext functions to Set functions and have it working to the same point I had it previously. Still can't update the SubmissionStatusValue.Selected.Value programmatically with a button click. 

Hi @CCJones 

I've done some playing around and have been able to get a dropdown to update,
I have a few values that are in my dropdown from a data source. i noticed updating the default variable also doesn't trigger a change so I have had to update the variable to set the default and then trigger a reset of the dropdown 

three properties for my dropdown are required for this to work

 

Items: 

//get items from a sharepoint list 

Filter(SmartScores,Question = 3) 

Default:

vcom

Reset:

myVar


Then I have the button

If(Dropdown4.Selected.Title = "No more than 5",
UpdateContext({vcom: "Between 5 and 10"}) &&
UpdateContext({myVar:true}));
UpdateContext({myVar:false})

 

 

Thank you for this!  I am not able to test right now, but will try to do so early next week. 

Hi, tried this and couldn't get it to work either. the Default property gives me an error that it is expecting a record when I apply the variable to it. It won't accept the text value that is stored. My Items is different than yours since it is looking up the values available from the choice column it is associated with:

Choices([@'SharePoint Support Requests'].'Submission Status')

Clearly, my "Items" property is pulling a record, so it expects a record from the variable. Am I going to have to make a lookup list or a collection that contains the choice values instead of using a choice column?

@CCJones 

I've tried it with choices as well and I'm not getting an error

I changed the items property on my dropdown to 

Choices([@CommunityTest].Status)

 

And my Button 

 

If(Dropdown4.Selected.Value = "Submitted",

UpdateContext({vcom: "Draft"}) &&
UpdateContext({myVar:true}));
UpdateContext({myVar:false})

 

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

Users online (698)