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

Disable Submit Button

Hi, 

 

I have a form that supposed to not let user to submit until the relevant fields have been filled up. Let me picture a clearer context on this situation: 

 

General Field:  Field A (text), B (text), C (text), D (lookup dropdown) are compulsory to be filled/ selected.

The lookup dropdown Field D let users to select a certain 'Instrument' and based on the instrument other fields E, F, G, H will be show/ hide based on the selected 'instrument'. 

 

Example: 'Instrument 1' selected - Field E show

               'Instrument 2' selected - Field F show

 

If Instrument 2 is selected, Field E will be hidden and user don't need to fill it up. 

 

My current formula only able to disable the submit button if the general field A, B, C, D are not filled up. I tried to fit in the rest of the Field EFGH, but I realized using && or || doesn't work for these non-general field. Is there any other way that I can disable them? 

 

Here's a sample of my current formula: 

 

If(!IsBlank(A) && !IsBlank(B) && !IsBlank(C) && !IsBlank(DateValue2_1) && !IsBlank(D.Selected), DisplayMode.Edit,DisplayMode.Disabled)

 

 

Thank you. 

2 ACCEPTED SOLUTIONS

Accepted Solutions
Pstork1
Most Valuable Professional
Most Valuable Professional

Here's the way it works

In OnStart and Screen.OnVisible

 

Set(emptyFields,<<number of empty fields on default screen>>)

 

In Each Control set OnSelect to the following to store whether the control is currently blank

 

UpdateContext({temp: IsBlank(Self.Text)})

 

 In Each Control set the OnChange to the following to update the emptyFields count as each field is changed. This will add 1 to EmptyFields if the field is currently filled in and the value deleted.  It will subtract 1 if the field is empty and filled in.  If only the value changes, not whether its empty or filled in then the count won't change.

 

If(
    temp,
    If(
        IsBlank(Self.Text),
        false,
        Set(
            emptyFields,
            emptyFields - 1
        )
    ),
    If(
        IsBlank(Self.Text),
        Set(
            emptyFields,
            emptyFields + 1
        ),
        false
    )
)

 

In the DisplayMode of the Button then its just

 

If(emptyFields <= 0,DisplayMode.Edit,DisplayMode.Disabled)

 

The one additional thing you would need to do is to change the EmptyFields count as additional controls are hidden or made visible based on the selection in the dropdown.  You may also have to adjust the formula for different types of controls. For example, a dropdown you would need to check if the selection is different from the default since they're never really blank.

EDIT: Here's the code to add the extra fields to the EmptyFields count when the user picks from the dropdown. Where Instrument makes one field visible and Instrument2 makes two fields visible.

   If(
        Self.Selected.Value = "Instrument1",
        Set(
            emptyFields,
            emptyFields + 1
        ),
        false
    );
    If(
        Self.Selected.Value = "Instrument2",
          Set(
            emptyFields,
            emptyFields + 2
        ),
        false
    )

 

There are a number of formulas here, but its essentially the same set for each control and the formula on the button is always the same. So this can expand to cover as many controls as you need. 

 



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

View solution in original post

@Xinlin

 

I think @Pstork1 approuch is excellent, but it can be difficult for beginners to extend. I got some time, so I did sort out Your problem. I hope this is what You are looking for.

 

SebS_1-1670096276742.gif

 

Here is the code I used for the button :

 

If(
    (!IsBlank(A) && !IsBlank(B) && !IsBlank(C) && !IsBlank(D.Selected.Value)) && (D.Selected.Value = "Instrument 1" && !IsBlank(E)) || (D.Selected.Value = "Instrument 2" && !IsBlank(F)) || (D.Selected.Value = "Instrument 3" && !IsBlank(G)) || (D.Selected.Value = "Instrument 4" && !IsBlank(H)),
    DisplayMode.Edit,
    DisplayMode.Disabled
)

 

And here is the Code I used for the visibility of buttons :

 

(D.Selected.Value = "Instrument 1")

 

Make sure to change numbers based on control from Instrument 1 to 2, and so go on.

 

Hope this helps


If you like this post, give a Thumbs up. Where it solved your request, Mark it as a Solution to enable other users to find it.

View solution in original post

13 REPLIES 13
SebS
Super User
Super User

Hi @Xinlin 

 

I'm not sure if I got it right.

 

You could use the visible property of each field E,F,G,H and place the formula there that will put the visible true or false base on the choice of Field D means when "Instrument 1" is selected, Field E will show up and rest of the field will stay hidden.

 

Try to place in the Visibility property of filed E code.

 

(D.Selected.Value = "Instrument 1")

 

if it returns true the Field E will become visible do same to other fields just change Instrument

 


If you like this post, give a Thumbs up. Where it solved your request, Mark it as a Solution to enable other users to find it.
cha_cha
Super User
Super User

Hello @Xinlin 

 

As I understand, please correct me if I'm wrong, that you want the button to be disabled until all the fields are filled. This code would be my suggestion.

 

If(IsBlank(A) Or IsBlank(B) Or IsBlank(C) Or IsBlank(DateValue2_1) Or IsBlank(D.Selected), DisplayMode.Disabled, DisplayMode.Edit)

 


  ✔️
Just in case you my answer helped you solve your problem, please mark/accept this as a SOLUTION This helps community members if they experience a similar issue in the future.

 

  🔗
🕸bistek.space  🐦 @cha_bistek  📺 @BisTekSpace 

 


 
Just in case my answer helped you solve your problem, please mark/accept this as a SOLUTION This helps community members if they experience a similar issue in the future.

 
bistek.space   @charv3n    @BisTekSpace 
Pstork1
Most Valuable Professional
Most Valuable Professional

When I am disabling a button based on Visible fields being filled in I usually do it by creating a counter of the fields to be filled in.  A baseline number is set when the screen becomes visible.  In the OnChange event for each field I then increment/decrement the number based on whether the field becomes filled in or is blanked out. The display mode of the button is set to If the number is less than or equal to zero.  

 

For your situation you would need to make one change.  When the dropdown selection is for Instrument is picked you would need to increase the counter for however many fields you are adding based on that pick.



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

Yes @cha_cha, I'm looking to disable the button but I'm trying to let Field EFGH to be included in the formula too but struggle to do it due to the dependency of Field D. 

 

@Pstork1 Can you roughly draft the formula so I could better picture how it could work? 

 

Thank you.

 

cha_cha
Super User
Super User

@Xinlin 

 

Can you please try this logic? I'm also keen on learning @Pstork1 on ways to this but would want to know if this kind of logic is possible.

If(
IsBlank(A) Or 
IsBlank(B) Or 
IsBlank(C) Or 
IsBlank(DateValue2_1) 
Or IsBlank(D.Selected)
Or (E.Visible And IsBlank(E))
Or (F.Visible And IsBlank(F))
Or (G.Visible And IsBlank(G))
Or (H.Visible And IsBlank(H))
, DisplayMode.Disabled, DisplayMode.Edit)

  


 
Just in case my answer helped you solve your problem, please mark/accept this as a SOLUTION This helps community members if they experience a similar issue in the future.

 
bistek.space   @charv3n    @BisTekSpace 
Pstork1
Most Valuable Professional
Most Valuable Professional

Here's the way it works

In OnStart and Screen.OnVisible

 

Set(emptyFields,<<number of empty fields on default screen>>)

 

In Each Control set OnSelect to the following to store whether the control is currently blank

 

UpdateContext({temp: IsBlank(Self.Text)})

 

 In Each Control set the OnChange to the following to update the emptyFields count as each field is changed. This will add 1 to EmptyFields if the field is currently filled in and the value deleted.  It will subtract 1 if the field is empty and filled in.  If only the value changes, not whether its empty or filled in then the count won't change.

 

If(
    temp,
    If(
        IsBlank(Self.Text),
        false,
        Set(
            emptyFields,
            emptyFields - 1
        )
    ),
    If(
        IsBlank(Self.Text),
        Set(
            emptyFields,
            emptyFields + 1
        ),
        false
    )
)

 

In the DisplayMode of the Button then its just

 

If(emptyFields <= 0,DisplayMode.Edit,DisplayMode.Disabled)

 

The one additional thing you would need to do is to change the EmptyFields count as additional controls are hidden or made visible based on the selection in the dropdown.  You may also have to adjust the formula for different types of controls. For example, a dropdown you would need to check if the selection is different from the default since they're never really blank.

EDIT: Here's the code to add the extra fields to the EmptyFields count when the user picks from the dropdown. Where Instrument makes one field visible and Instrument2 makes two fields visible.

   If(
        Self.Selected.Value = "Instrument1",
        Set(
            emptyFields,
            emptyFields + 1
        ),
        false
    );
    If(
        Self.Selected.Value = "Instrument2",
          Set(
            emptyFields,
            emptyFields + 2
        ),
        false
    )

 

There are a number of formulas here, but its essentially the same set for each control and the formula on the button is always the same. So this can expand to cover as many controls as you need. 

 



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

@cha_cha Thanks for your input! Tried the provided logic but it doesn't work the way I wish it to be. 

 

Example: 

If Instrument 1 selected: Field E visible, submit button disabled until filled. (nice!)

If Instrument 2 selected: Field F visible, but submit button is disabled because of the condition set for Field E. 

 

Hope this example could provide a better context of the current challenge I'm facing right now. 

This is really nice approuch and good to know. Thank You for sharing it @Pstork1 


If you like this post, give a Thumbs up. Where it solved your request, Mark it as a Solution to enable other users to find it.

Thank you @Pstork1! Can I set condition for the number of counts on the button depending on the number of fields appearing based on the instruments? 


Assuming the total emptyField = 25, 

In Instrument 1, there will be 15 emptyField

In Instrument 2, there will be 9 emptyField

 

I tried to set the button to something like this but it came back with error. 

If(D.Selected.Value= "Instrument 1", (emptyFields <= 15, DisplayMode.Edit,DisplayMode.Disabled)

 

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,528)