cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
SamB2
Helper III
Helper III

Help with Display Mode

I have a PowerApps form where I have two buttons at the bottom (1. Save as Draft & 2. Submit). The only required field I have is Title in order for a user to be able to save the form as draft. 

 

The OnSelect property on the Save as Draft button is as follows:

 

If(SharePointForm1.Valid, UpdateContext({locIsSubmit: false}); SubmitForm(SharePointForm1); Notify("Form Saved Successfully",NotificationType.Success); Navigate('Previous Submissions'), Notify("Unable to save form. Please ensure 'Title' has been populated and try again.", NotificationType.Error))

 

The above works fine. My issue is with the Submit button. To be able to Submit the form, all fields in the form are mandatory which I have also got working by adding "locIsSubmit" into the required property of each field.

 

However, I would like to make the display mode of the Submit button disabled until all fields on the form are populated. If I use this expression "If(SharePointForm1.Valid, DisplayMode.Edit, DisplayMode.Disabled)" the submit button becomes clickable as soon as the Title field is populated. 

 

I would also like to Navigate to the "Success Screen" when the form has been submitted successfully. However currently, the form is navigating the success screen regardless of whether the form is valid or not. 

 

Any help would be much appreciated!

1 ACCEPTED SOLUTION

Accepted Solutions
madlad
Super User
Super User

@SamB2 

I think I see what you mean with your form validation now. locIsSubmit is being changed to determine the validation when the Save Draft button is submitted, right? I think there's two things you want to do here.

1. Make sure locIsSubmit is set to true by default - likely in this screen's OnVisible.

2. Change the save draft code to set it to false before the if function - something like:

 

UpdateContext({locIsSubmit: false});
If(
  SharePointForm1.Valid,
  SubmitForm(SharePointForm1);
  Notify("Form Saved Successfully",NotificationType.Success);,
  Notify("Unable to save form. Please ensure 'Title' has been populated and try again.", 
  NotificationType.Error)
)

 

As this will ensure that the Save Draft button is only checking for the validation of the title field. 

 

For navigating to the success screen - if you only want it to happen when they press the submit button, perhaps in the form's onSuccess, use the exact same if function as in the Submit buttons display mode - just replace "DisplayMode.Edit" with "Navigate(Success Screen)", and replace DisplayMode.Disabled with "Navigate('Previous Submissions')".

 

 

If none of this works, another option(although its a bit more inconvenient)

The easiest(but much longer) way to solve this in my opinion is, since the validation of the form is being based on only the title field most likely, you could try set it to something like:

 

If(
  !IsBlank(*TitleField*.Text) &&
  !IsBlank(*DatePicker1*.SelectedDate) &&
  !IsBlank(DatePicker2*.SelectedDate) &&
  !IsBlank(*WGCField*.Text) &&
  !IsEmpty(*AttachmentsField*.Attachments) &&
  ect.,
  DisplayMode.Edit,
  DisplayMode.Disabled
)

 

Using something like this as your forms visibility and including all mandatory fields is a bit longer, but its a bit more clearly displayed for troubleshooting. Just make sure to put in appropriate control names.

View solution in original post

15 REPLIES 15
madlad
Super User
Super User

Do you have all fields set as required?

Every data card in a form has a property(visible in advanced settings) named 'Required'; which is based on the datasource by default, but can be manually changed.

Even if they do somehow try to submit the form with not all required fields full, it will throw an error instead of submitting.

 

For each datacard, change the required to true and this should have the effect you want.

 

For your navigation, a safe bet is to have it in the forms 'OnSuccess' property.

 

Another thing you can do, since for saving you only need Title populated, is manually check the values of specific controls within a form - but this takes up quite a bit more space, but it's useful if you only need some fields to do one action, but need different ones for another.

 

Hope this helps!

SamB2
Helper III
Helper III

Hi @madlad - thanks for the response. 

 

The only field set as required is Title. If I set all fields to required, then users will not be able to Save the form as draft (hence why I have created the 'locIsSubmit' variable). 

 

Again with the OnSuccess property, I have tried this and users are getting directed to the Success Page when they are Saving the form as draft. 

I think the reason for the onsuccess property changing screens is because you're submitting the form in your save button - since only title is required to be valid, it's submitting the form. 

SamB2
Helper III
Helper III

Yes that is exactly the reason, hence why I have created the "locIsSubmit" variable that sets the Status Column to either draft or submitted depending on whether Save as Draft or Submit is pressed respectively. 

 

Therefore, simply Navigating to the Success Screen 'OnSuccess' of the form won't work in this instance. I need to find a way to navigate to the success screen only if Submit is pressed. (Save still submits the form and creates an item in the SharePoint list but leaves the Status set as Draft). 

 

I also need to find a way for the Submit button to only be DisplayMode.Edit when ALL fields are complete, despite only the Title field being required (which works for the Save as draft button). 

Hi @SamB2 ,

 

I believe that because you're using the navigate on the "OnSuccess" property of form, it will always go to the success screen because even draft submission is success for the form.

What you can do is remove the navigate code from "OnSuccess" and use only in the Submit button.

 

2nd for the problem where you have to disable the button until all fields are filled,

you can make all the fields requried by passing your variable "locIsSubmit" in them, whenever the draft button will be pressed they all will be false and Title will be added, and when the Submit button will be pressed, at the start you can make this variable true UpdateContext({locIsSubmit: false}); SubmitForm(SharePointForm1); so it will not submit until all fields are filled, and then you can pass the following code in buttons DisplayMode property:

 

If(SharePointForm1.Valid,DisplayMode.Edit,DisplayMode.Disabled)

 

 

Do let me know if you see any challenges, I am always happy to help.

Regards,
Faisal

if this reply/solution works Mark it as the solution and give a thumbs-up.

Thanks @Faisal__Wasim .

 

Re the second point. This is exactly what I have done. This works fine when form is in Edit mode, however when in New form mode, it only thinks the Title field is required despite me setting the Required property as "locIsSubmit" on all other fields. So even though it doesn't let me submit in New Form mode with just the title populated, the Submit button instantly becomes enabled when the title field is populated.

Hi @SamB2,

I believe if I understand it right, you want to use the submit button to submit new entries well right ? 
If yes, on the Submit Buttons onselect, are you updating the variable to true at the start? 
Thanks let me know 

SamB2
Helper III
Helper III

Yes that is correct, it is a long form so the idea is that a user can Save a form as draft with as many of the fields blank (except from the title), and then when all fields are populated, they can hit Submit which will submit the form. 

 

The OnSelect property of the Submit button is as per below:

 

UpdateContext({locIsSubmit: true}); SubmitForm(SharePointForm1);

 

As you can see from below screenshot, the Submit button is in 'Edit' display mode despite the fields above it being blank (and Title is populated):

 

submit button.JPG

 

When Title is blank the display mode is set to disabled:

 

submit disabled.JPG

 

The DisplayMode property on the Submit button is below:

 

If(SharePointForm1.Valid, DisplayMode.Edit, DisplayMode.Disabled)

Hi @SamB2

If you dont mind, can you kindly show the code written in required property of WGC Outcome and the Dates above. Thanks

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 (1,850)