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

Trying to convert user inputted numbers into phone number format in PowerApps form

Hello everyone,

 

Just as a disclaimer, I have been working on this issue for the past few hours, and have done extensive research and basically read through every bit of information I could find, but I am still having trouble.

 

I have a PowerApps form that is connected to a SharePoint Online list. We have a phone number field, and I am trying to basically transform the numbers people input into the US xxx-xxx-xxxx format. I've tried using a bunch of different TextFormat.Number related modifications, but to no avail. I've also tried converting the input method/type to Text, and using TextFormat.Text=Text(Value(DataCardValue6),"[$-en-US](000)-000-0000").

 

Anyways, I'll be incredibly grateful for any help that anyone can provide. Thank you so much in advance! 

 

Edit: I've also tried TextFormat.Text=Text(Value(DataCardValue6.Text),"[$-en-US](000)-000-0000"). And a lot of variations on this. I keep getting exceptions, so I obviously don't know what I'm doing. 🙂

3 ACCEPTED SOLUTIONS

Accepted Solutions

You can use it with an If condition in the OnSelect property of Submit button/icon. If the format is true it process SubmitForm otherwise it returns false.

 

If(IsMatch(PhoneNumberField.Text, LeftParen & Digit & Digit & Digit & RightParen & Hyphen & Digit & Digit & Digit & Hyphen & Digit & Digit & Digit & Digit), SubmitForm(EditForm), false)

This isn't to user friendly because the user doesn't know why the form wasn't saved. To make this more user friendly you would need to add a label to the form to display the error message. Then you would need to replace false in the If condition with some code that would make the error message label visible.

 

 



--------------------------------------------------------------------------------
If this post helps answer your question, please click on “Accept as Solution” to help other members find it more quickly. If you thought this post was helpful, please give it a Thumbs Up.

View solution in original post

To enhance what @Jeff_Thorpe is suggesting, I would say that you could place the IsMatch expression in the DsiplayMode property of the submit button, so that it is disabled unless the input text is in the format you want.  This way the button is not pushable.

Something like this for the DisplayMode property:

If(IsMatch(PhoneNumberField.Text, LeftParen & Digit & Digit & Digit & RightParen & Hyphen & Digit & Digit & Digit & Hyphen & Digit & Digit & Digit & Digit), DisplayMode.Edit, DisplayMode.Disabled)

View solution in original post

11 REPLIES 11
Meneghino
Community Champion
Community Champion

Hi @nealhicks1

 

Which of the following are you tring to do?

 

1) Ensure that the input is in the format (xxx)-xxx-xxxx and only accept such input

OR

2) Accept any reasonable input (like 1234567890) and convert it to (123)-456-7890 when updating the SP list

 

The first task is obviously much easier. All it requires is to have your text input in text mode and use the IsMatch function in a simple way.  For example to enable the save button (via the DisplayMode property) only if IsMatch is positive.

 

The second task requires to define which patterns are acceptable and have a correspondingly complex IsMatch condition or series of conditions to enable the save button.  Then you will need a parsing function using string functions depending on the pattern of the input.

 

Hope this helps

Hello @Meneghino,

 

Thanks for the response! Smiley Happy

 

I'm not strong with the coding, so I would vote on whichever option would require less coding to get working. 🙂

 

If I were wanting to go with option 1, how do I go about actually implementing the necessary IsMatch condition?

 

Also, I'm having a problem where any inputted numbers are basically turned into.. well, say that 1234567890 is inputted, then it will turn that into 1,234,567,890, displaying commas and everything. So I need to somehow ensure that the numbers are displayed in the 123-456-7890 format.

 

I really appreciate your help with this!

The phone number field will need to be a text field. The IsMatch function would look like this:

 

IsMatch(PhoneNumberField.Text, LeftParen & Digit & Digit & Digit & RightParen & Hyphen & Digit & Digit & Digit & Hyphen & Digit & Digit & Digit & Digit)

It will return true if it matches the format (###)-###-#### otherwise it returns false.



--------------------------------------------------------------------------------
If this post helps answer your question, please click on “Accept as Solution” to help other members find it more quickly. If you thought this post was helpful, please give it a Thumbs Up.

Apologies for my ignorance, but where exactly do I input that string? I've been looking all through the Properties and Advanced tabs, but I can't seem to find the right place for that. I am very new at PowerApps, so I apologize for the trouble!

 

Also, @Jeff_Thorpe, thanks for helping me out with both my threads. 🙂

You can use it with an If condition in the OnSelect property of Submit button/icon. If the format is true it process SubmitForm otherwise it returns false.

 

If(IsMatch(PhoneNumberField.Text, LeftParen & Digit & Digit & Digit & RightParen & Hyphen & Digit & Digit & Digit & Hyphen & Digit & Digit & Digit & Digit), SubmitForm(EditForm), false)

This isn't to user friendly because the user doesn't know why the form wasn't saved. To make this more user friendly you would need to add a label to the form to display the error message. Then you would need to replace false in the If condition with some code that would make the error message label visible.

 

 



--------------------------------------------------------------------------------
If this post helps answer your question, please click on “Accept as Solution” to help other members find it more quickly. If you thought this post was helpful, please give it a Thumbs Up.

To enhance what @Jeff_Thorpe is suggesting, I would say that you could place the IsMatch expression in the DsiplayMode property of the submit button, so that it is disabled unless the input text is in the format you want.  This way the button is not pushable.

Something like this for the DisplayMode property:

If(IsMatch(PhoneNumberField.Text, LeftParen & Digit & Digit & Digit & RightParen & Hyphen & Digit & Digit & Digit & Hyphen & Digit & Digit & Digit & Digit), DisplayMode.Edit, DisplayMode.Disabled)

Thanks for all the suggestions!

 

So when you say that I could place the IsMatch expression in the DisplayMode property of the submit button, from where do I go about doing that? In the Advanced tab? I am trying to find the right place to insert that IsMatch code, but I am not sure where I should do that.

 

Sorry for the likely extreme level of newbie-ness!

 

 

1.JPG

Thank you very much! I think I'm good with this, now.

 

I appreciate everyone's help!

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

Top Solution Authors
Top Kudoed Authors
Users online (2,253)