cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
LilaBeth
Frequent Visitor

Submitting form only when certain criteria is met

I have a form that has 5 separate fields that have to be filled in a certain way before the form is submitted. I have Business_EIN_Value should be 9 digits. Individual_SSN_Value should be 9 digits. Customer_ZIP_Value should be 5 digits. Business_Telephone_Value should be 10 digits. And finally Contact_Email_Value should be set up in an email format. Is there a way to create a formula that will look at all of these factors and not allow the user to submit the form without having the items filled in correctly.

 

I've been able to do this before with just one using If(IsMatch(Business_EIN_Value.Text, Digit & Digit & Digit & Digit & Digit & Digit & Digit & Digit & Digit), SubmitForm(AppForm);ResetForm(AppForm);Navigate(SuccessScreen), Notify("Please input a valid 9 digit Business EIN", Error))

 

However, I'm not sure how to do the email at all and I can't get the If IsMatch to nest correctly and I'm not sure if there's a way to do what I'm wanting. Any help, any direction would be greatly appreciated. 

7 REPLIES 7

@LilaBeth 

Funny...I was just in the middle of putting together a video to really demonstrate this. 

There are a variety of ways to go about it.  I will present a simple one for you.

 

1) Put a Toggle on your screen (call it tglFormValid) and set the Default property to the following:

yourForm.Valid &&
IsMatch(yourForm.Updates.Business_EIN_Value, "\d{9}") &&
IsMatch(yourForm.Updates.Contact_Email, Email) &&
IsMatch(yourForm.Updates.ZipField, "\d{5}") &&
IsMatch(yourForm.Updates.BusinessPhoneField, "\d{10}")

Replace all the names after the Updates. to be the correct names for your fields.  You should, as much as possible, reference the Updates property of the Form to get the actual values and not the controls in the datacards.

 

2) On the DisplayMode property of your Submit button, put the following formula:

If(tglFormValid.Value, Edit, Disabled)

 

Now your button will be disabled if the criteria for your fields is not met. 

 

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!

@RandyHayes 

 

I've tried your suggestion and it continues to give me 4 errors. It's giving me The function 'IsMatch' has some invalid arguments. Invalid use of '.' and Name isn't valid. This identifier isn't recognized. And the final error is This rule creates a circular reference between properties, which is not allowed. A property cannot reference itself or other properties affected by its value. 

 

I've changed all of the fields to match the name of the fields in my form. If I remove the yourform.Updates (I have changed yourform to match my form's name) and add .text to the end (ex. Business_EIN_Value.text) then the errors goes away and I'm not quite sure what to do. 

@LilaBeth 

Sorry for the delay.

Are you still having the problem?

If so, can you tell me where you have the controls that I outlined in my solution?  You should not be getting a circular reference unless you have put any of these controls (the toggle or the button) INSIDE of your form...they should be on the screen only.

The yourForm.Updates.fieldName should all be set as suggested rather than referring to the control in the form.  You should have replaced yourForm with the name of your form and the fieldName with the appropriate field name defined in the datasource of your form.

If you are still seeing an issue, please send a screenshot of the formula with the errors visible.

_____________________________________________________________________________________
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!

@RandyHayes 

 

No problem. I must apologize for the delay. I misunderstood what you meant and that caused the circular reference. I moved the toggle from the form to the screen and that worked to remove the circular reference. However, I'm still receiving the same Name isn't valid, invalid use of ., and The function "IsMatch" has some invalid arguments. I've changed the your Form to match my form's name and changed the fieldName to match my fields and I'm still getting the same error. I've added a screenshot of the form and of the errors, let me know if you need more clear screenshots of the errors.

 

LilaBeth_0-1607380742208.png

 

@LilaBeth 

Sorry to drop the ball on this again.  Did you figure it out or still need some help?

_____________________________________________________________________________________
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!

@RandyHayes 

 

No worries. I was able to get it to work by removing yourForm.Updates and adding .text. For example I changed it to IsMatch(Business_EIN_Value.text, "\d{9}") and the error disappears. I'm not sure the importance of yourForm.Updates, but by removing I was able to get it to work.

@LilaBeth 

The significance of the .Updates is that, in general, you should not refer to the controls inside the form datacards.  The reason is that you can change those control types in the form edit fields and, if you do, it will break the formulas.  Also, the .Updates is the "real" value that will be written to the datasource in the SubmitForm.  Forms allow you to alter the Update property of the datacard to alter what is written.  If you want to validate that value (rather than the raw control in the form), then you should rely on the Updates property of the form instead.

It's not a "rule", but it is a best practice to get in the habit of doing.

 

I did notice in your screenshot that you had .Update instead of .Updates in your formula - perhaps that was the cause of the error for you.

 

Glad you have been able to move forward though.

_____________________________________________________________________________________
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!

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