cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
Anonymous
Not applicable

Max Length on text field + automatic dashes in between letters?

Hello,

 

I would like to have a text field dedicate to a Serial Number that contains up to 12 digits, the digits normally come separated by 2. example: 12-34-56-78-90-12. Is it possible to make them automatically add the dash and only allow 12 numbers/letters to be entered?

 

Thank you in advanced! 

3 ACCEPTED SOLUTIONS

Accepted Solutions
mdevaney
Super User
Super User

@Anonymous

You can restrict the number of digits allowed by changing the MaxLength property of the Text Input to 12.  But there is no way to have the dashes automatically entered.

The only workaround I can think of is to have 6 text fields, each with a 2 digit MaxLength side-by-side.  Then you could join their text into a single string by doing this

 

TextInput1.Text&"-"&TextInput2.Text&"-"&TextInput3.Text&"-"&
TextInput4.Text&"-"&TextInput5.Text&"-"&TextInput6.Text

 

The output would look exactly like your example

 

---
Please click "Accept as Solution" if my post answered your question so that others may find it more quickly. If you found this post helpful consider giving it a "Thumbs Up."

View solution in original post

yashag2255
Super User
Super User

Hi @Anonymous 

 

There is no direct way to add dashes to the input control. As a workaround to this, you can show an error message when the user has not entered the dashes in between by using the below configuration:
 
1) If you are okay with adding an error label then :
Add a Text Label and add the Text property as: "The Input should be in format XX-XX-XX-XX-XX-XX"
Text Label -> Color: If(IsMatch(TextInput1.Text,Match.Digit&Match.Digit&"-"&Match.Digit&Match.Digit&"-"&Match.Digit&Match.Digit&"-"&Match.Digit&Match.Digit&"-"&Match.Digit&Match.Digit&"-"&Match.Digit&Match.Digit),RGBA(0, 0, 0, 1),Red)
Text Label -> Visible : If(IsMatch(TextInput1.Text,Match.Digit&Match.Digit&"-"&Match.Digit&Match.Digit&"-"&Match.Digit&Match.Digit&"-"&Match.Digit&Match.Digit&"-"&Match.Digit&Match.Digit&"-"&Match.Digit&Match.Digit),false,true)
 
2) If you want to restrict the length of input, you can set the "Maximum Length" property of the text input control to 12. This will not allow user to add values after 12 digits and if you want to restrict to only numbers, then you can set the Format property to Number. This will not allow dashes.
 
 
Hope this Helps!

If this reply has answered your question or solved your issue, please mark this question as answered. Answered questions helps users in the future who may have the same issue or question quickly find a resolution via search. If you liked my response, please consider giving it a thumbs up. THANKS!

View solution in original post

poweractivate
Most Valuable Professional
Most Valuable Professional

@Anonymous 

 

@yashag2255 and @mdevaney  - great approaches - in combination with your approaches I have another specific idea for implementation of this use case that can be considered as well.

 

Although PowerApps does not currently have Input Mask functionality out of the box, I have a custom solution for you with 8 digits - it can be so easily adapted to 12 digits yourself if you just add 4 more entries to the collection. You can combine this with the ideas by @mdevaney  of restricting the max input of the field to 12.

 

Step 1: OnVisible of your screen that has the control on it - initialize a collection with a series of columns that have the lengths, and the mask you want to render for each possible length. Here I do it for up to 8 digits. You can extend this to 12 by adding four more relevant entries to this collection

 

 

 

 

 

ClearCollect(MYCOLL,{myLen:1,myMask:"#"},{myLen:2,myMask:"##"},{myLen:3,myMask:"##-#"},{myLen:4,myMask:"##-##"},{myLen:5,myMask:"##-##-#"},{myLen:6,myMask:"##-##-##"},{myLen:7,myMask:"##-##-##-#"},{myLen:8,myMask:"##-##-##-##"})

 

 

 

 

 

OnVisSerial1.png

 

Step 2: 

 

OnChange of your input field where you are taking the input, use this code:

 

 

 

 

 

Set(MYVAR,Value(MyNumberInput1.Text))

 

 

 

 

 

OnChangeNumInput1.png

 

 

 

Step 3: Make sure Format property of your Input control is set to Number - this is similar to suggestions before. You can also use the MaxLength suggestion as well here, as mentioned by @mdevaney to restrict the max input length to 12 (I don't explicitly use it in this sample, but you can do this as well).

 

FormatNumInput1.png

 

Step 4: use this code:

 

 

(on the Text property of the Label): 

 

 

Text(MYVAR,LookUp(MYCOLL,Len(Text(MYVAR)) = myLen,myMask))

 

 

 

 

 

TextPropLookup.png

 

Step 5: You did it!

 

Note - because it's OnChange, make sure when testing it, that you enter something in the input field, then press somewhere else on the screen to focus out of the field, that triggers the onChange. If you need to do it other than OnChange i.e. you want to avoid the need to focus out of the field, you may need to use a trick and adapt App Timer Wait Recipe and have a repeating timer that just about every 500 milliseconds or so does the equivalent of Step 2 - then you can have it work without focusing out of the field every time you modify the value.

 

In this specific tested example above:

 

When someone types in 1 you should get 1

When someone types in 12 you should get 12

When someone types in 123 you should get 12-3

When someone types in 1234 you should get 12-34

When someone types in 12345 you should get 12-34-5

When someone types in 123456 you should get 12-34-56

When someone types in 1234567 you should get 12-34-56-7

When someone types in 12345678 you should get 12-34-56-78

 

You can adjust the masks as needed for your use case, add new masks, etc.

 

Let's say you don't want to allow an odd number of digits. Here is quick approach to test quickly -  you may want to go for something a little more sophisticated in your case - but here would be the basics of one approach: You can replace the collection elements in our example above for myLen for 1, 3, 5, 7, etc. with something like CANNOT BE ODD NUMBER OF DIGITS for the myMask values - and that would display on the text label. On your button or other place, you can check for this value and disable the button if that's the value of the label - then an odd number of digits wouldn't be allowed in that case. 

 

@Anonymous let me know if the above approach helped you.

 

 

View solution in original post

6 REPLIES 6
mdevaney
Super User
Super User

@Anonymous

You can restrict the number of digits allowed by changing the MaxLength property of the Text Input to 12.  But there is no way to have the dashes automatically entered.

The only workaround I can think of is to have 6 text fields, each with a 2 digit MaxLength side-by-side.  Then you could join their text into a single string by doing this

 

TextInput1.Text&"-"&TextInput2.Text&"-"&TextInput3.Text&"-"&
TextInput4.Text&"-"&TextInput5.Text&"-"&TextInput6.Text

 

The output would look exactly like your example

 

---
Please click "Accept as Solution" if my post answered your question so that others may find it more quickly. If you found this post helpful consider giving it a "Thumbs Up."

@Anonymous 

I edited my post above with a workaround.  Let me know if you saw it 🙂

yashag2255
Super User
Super User

Hi @Anonymous 

 

There is no direct way to add dashes to the input control. As a workaround to this, you can show an error message when the user has not entered the dashes in between by using the below configuration:
 
1) If you are okay with adding an error label then :
Add a Text Label and add the Text property as: "The Input should be in format XX-XX-XX-XX-XX-XX"
Text Label -> Color: If(IsMatch(TextInput1.Text,Match.Digit&Match.Digit&"-"&Match.Digit&Match.Digit&"-"&Match.Digit&Match.Digit&"-"&Match.Digit&Match.Digit&"-"&Match.Digit&Match.Digit&"-"&Match.Digit&Match.Digit),RGBA(0, 0, 0, 1),Red)
Text Label -> Visible : If(IsMatch(TextInput1.Text,Match.Digit&Match.Digit&"-"&Match.Digit&Match.Digit&"-"&Match.Digit&Match.Digit&"-"&Match.Digit&Match.Digit&"-"&Match.Digit&Match.Digit&"-"&Match.Digit&Match.Digit),false,true)
 
2) If you want to restrict the length of input, you can set the "Maximum Length" property of the text input control to 12. This will not allow user to add values after 12 digits and if you want to restrict to only numbers, then you can set the Format property to Number. This will not allow dashes.
 
 
Hope this Helps!

If this reply has answered your question or solved your issue, please mark this question as answered. Answered questions helps users in the future who may have the same issue or question quickly find a resolution via search. If you liked my response, please consider giving it a thumbs up. THANKS!
poweractivate
Most Valuable Professional
Most Valuable Professional

@Anonymous 

 

@yashag2255 and @mdevaney  - great approaches - in combination with your approaches I have another specific idea for implementation of this use case that can be considered as well.

 

Although PowerApps does not currently have Input Mask functionality out of the box, I have a custom solution for you with 8 digits - it can be so easily adapted to 12 digits yourself if you just add 4 more entries to the collection. You can combine this with the ideas by @mdevaney  of restricting the max input of the field to 12.

 

Step 1: OnVisible of your screen that has the control on it - initialize a collection with a series of columns that have the lengths, and the mask you want to render for each possible length. Here I do it for up to 8 digits. You can extend this to 12 by adding four more relevant entries to this collection

 

 

 

 

 

ClearCollect(MYCOLL,{myLen:1,myMask:"#"},{myLen:2,myMask:"##"},{myLen:3,myMask:"##-#"},{myLen:4,myMask:"##-##"},{myLen:5,myMask:"##-##-#"},{myLen:6,myMask:"##-##-##"},{myLen:7,myMask:"##-##-##-#"},{myLen:8,myMask:"##-##-##-##"})

 

 

 

 

 

OnVisSerial1.png

 

Step 2: 

 

OnChange of your input field where you are taking the input, use this code:

 

 

 

 

 

Set(MYVAR,Value(MyNumberInput1.Text))

 

 

 

 

 

OnChangeNumInput1.png

 

 

 

Step 3: Make sure Format property of your Input control is set to Number - this is similar to suggestions before. You can also use the MaxLength suggestion as well here, as mentioned by @mdevaney to restrict the max input length to 12 (I don't explicitly use it in this sample, but you can do this as well).

 

FormatNumInput1.png

 

Step 4: use this code:

 

 

(on the Text property of the Label): 

 

 

Text(MYVAR,LookUp(MYCOLL,Len(Text(MYVAR)) = myLen,myMask))

 

 

 

 

 

TextPropLookup.png

 

Step 5: You did it!

 

Note - because it's OnChange, make sure when testing it, that you enter something in the input field, then press somewhere else on the screen to focus out of the field, that triggers the onChange. If you need to do it other than OnChange i.e. you want to avoid the need to focus out of the field, you may need to use a trick and adapt App Timer Wait Recipe and have a repeating timer that just about every 500 milliseconds or so does the equivalent of Step 2 - then you can have it work without focusing out of the field every time you modify the value.

 

In this specific tested example above:

 

When someone types in 1 you should get 1

When someone types in 12 you should get 12

When someone types in 123 you should get 12-3

When someone types in 1234 you should get 12-34

When someone types in 12345 you should get 12-34-5

When someone types in 123456 you should get 12-34-56

When someone types in 1234567 you should get 12-34-56-7

When someone types in 12345678 you should get 12-34-56-78

 

You can adjust the masks as needed for your use case, add new masks, etc.

 

Let's say you don't want to allow an odd number of digits. Here is quick approach to test quickly -  you may want to go for something a little more sophisticated in your case - but here would be the basics of one approach: You can replace the collection elements in our example above for myLen for 1, 3, 5, 7, etc. with something like CANNOT BE ODD NUMBER OF DIGITS for the myMask values - and that would display on the text label. On your button or other place, you can check for this value and disable the button if that's the value of the label - then an odd number of digits wouldn't be allowed in that case. 

 

@Anonymous let me know if the above approach helped you.

 

 

Anonymous
Not applicable

Thank you very much. This is very helpful!

I have a similar problem, but I can't solve it. In my case, there is a letter (from a to z) in the first place of my pattern (e.g: Z1234-12345-12345). Do you know a workaround?

 

My post: https://powerusers.microsoft.com/t5/Building-Power-Apps/How-to-autoformatting-a-textinput-while-the-...

 

Thanks

Helpful resources

Announcements

Update! June 13th, Community Ambassador Call for User Group Leaders and Super Users

Calling all Super Users & User Group Leaders     UPDATE:  We just wrapped up June's Community Ambassador monthly calls for Super Users and User Group Leaders. We had a fantastic call with lots of engagement. We are excited to share some highlights with you!    Big THANK YOU to our special guest Thomas Verhasselt, from the Copilot Studio Product Team for sharing how to use Power Platform Templates to achieve next generation growth.     A few key takeaways: Copilot Studio Cookbook Challenge:  Week 1 results are posted, Keep up the great work!Summer of Solutions:  Starting on Monday, June 17th. Just by providing solutions in the community, you can be entered to win tickets to Power Platform Community Conference.Super User Season 2: Coming SoonAll communities moving to the new platform end of July We also honored two different community members during the call, Mohamed Amine Mahmoudi and Markus Franz! We are thankful for both leaders' contributions and engagement with their respective communities. 🎉   Be sure to mark your calendars and register for the meeting on July 11th and stay up to date on all of the changes that are coming. Check out the Super User Forum boards for details.   We're excited to connect with you and continue building a stronger community together.   See you at the call!  

Win free tickets to the Power Platform Conference | Summer of Solutions

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**

Copilot Cookbook Challenge | Week 2 Results | Win Tickets to the Power Platform Conference

We are excited to announce the "The Copilot Cookbook Community Challenge is a great way to showcase your creativity and connect with others. Plus, you could win tickets to the Power Platform Community Conference in Las Vegas in September 2024 as an amazing bonus.   Two ways to enter: 1. Copilot Studio Cookbook Gallery: https://aka.ms/CS_Copilot_Cookbook_Challenge 2. Power Apps Copilot Cookbook Gallery: https://aka.ms/PA_Copilot_Cookbook_Challenge   There will be 5 chances to qualify for the final drawing: Early Bird Entries: March 1 - June 2Week 1: June 3 - June 9Week 2: June 10 - June 16Week 3: June 17 - June 23Week 4: June 24 - June 30     At the end of each week, we will draw 5 random names from every user who has posted a qualifying Copilot Studio template, sample or demo in the Copilot Studio Cookbook or a qualifying Power Apps Copilot sample or demo in the Power Apps Copilot Cookbook. Users who are not drawn in a given week will be added to the pool for the next week. Users can qualify more than once, but no more than once per week. Four winners will be drawn at random from the total qualifying entrants. If a winner declines, we will draw again at random for the next winner.  A user will only be able to win once. If they are drawn multiple times, another user will be drawn at random. Prizes:  One Pass to the Power Platform Conference in Las Vegas, Sep. 18-20, 2024 ($1800 value, does not include travel, lodging, or any other expenses) Winners are also eligible to do a 10-minute presentation of their demo or solution in a community solutions showcase at the event. To qualify for the drawing, templates, samples or demos must be related to Copilot Studio or a Copilot feature of Power Apps, Power Automate, or Power Pages, and must demonstrate or solve a complete unique and useful business or technical problem. Power Automate and Power Pagers posts should be added to the Power Apps Cookbook. Final determination of qualifying entries is at the sole discretion of Microsoft. Weekly updates and the Final random winners will be posted in the News & Announcements section in the communities on July 29th, 2024. Did you submit entries early?  Early Bird Entries March 1 - June 2:  If you posted something in the "early bird" time frame complete this form: https://aka.ms/Copilot_Challenge_EarlyBirds if you would like to be entered in the 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. Copilot Cookbook Gallery:Power Apps Cookbook Gallery:1.  @Mathieu_Paris 1.   @SpongYe 2.  @Dhanush 2.   @Deenuji 3.  n/a3.   @Nived_Nambiar  4.  n/a4.   @ManishSolanki 5.  n/a5.    n/a   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. Copilot Cookbook Gallery:Power Apps Cookbook Gallery:1. Kasun_Pathirana1. ManishSolanki2. cloudatica2. madlad3. n/a3. SpongYe4. n/a4. n/a5. n/a5. n/a

Celebrating the June Super User of the Month: Markus Franz

Markus Franz is a phenomenal contributor to the Power Apps Community. Super Users like Markus inspire others through their example, encouragement, and active participation.    The Why: "I do this to help others achieve what they are trying to do. As a total beginner back then without IT background I know how overwhelming things can be, so I decided to jump in and help others. I also do this to keep progressing and learning myself." Thank you, Markus Franz, for your outstanding work! Keep inspiring others and making a difference in the community! 🎉  Keep up the fantastic work! 👏👏   Markus Franz | LinkedIn  Power Apps: mmbr1606  

Your Moment to Shine: 2024 PPCC’s Got Power Awards Show

For the third year, we invite you, our talented community members, to participate in the grand 2024 Power Platform Community Conference's Got Power Awards. This event is your opportunity to showcase solutions that make a significant business impact, highlight extensive use of Power Platform products, demonstrate good governance, or tell an inspirational story. Share your success stories, inspire your peers, and show off some hidden talents.  This is your time to shine and bring your creations into the spotlight!  Make your mark, inspire others and leave a lasting impression. Sign up today for a chance to showcase your solution and win the coveted 2024 PPCC’s Got Power Award. This year we have three categories for you to participate in: Technical Solution Demo, Storytelling, and Hidden Talent.      The Technical solution demo category showcases your applications, automated workflows, copilot agentic experiences, web pages, AI capabilities, dashboards, and/or more. We want to see your most impactful Power Platform solutions!  The Storytelling category is where you can share your inspiring story, and the Hidden Talent category is where your talents (such as singing, dancing, jump roping, etc.) can shine! Submission Details:  Fill out the submission form https://aka.ms/PPCCGotPowerSignup by July 12th with details and a 2–5-minute video showcasing your Solution impact. (Please let us know you're coming to PPCC, too!)After review by a panel of Microsoft judges, the top storytellers will be invited to present a virtual demo presentation to the judges during early August. You’ll be notified soon after if you have been selected as a finalist to share your story live at PPCC’s Got Power!  The live show will feature the solution demos and storytelling talents of the top contestants, winner announcements, and the opportunity to network with your community.  It's not just a showcase for technical talent and storytelling showmanship, show it's a golden opportunity to make connections and celebrate our Community together! Let's make this a memorable event! See you there!   Mark your calendars! Date and Time: Thursday, Sept 19th Location: PPCC24 at the MGM Grand, Las Vegas, NV 

Tuesday Tip | Accepting Solutions

It's time for another TUESDAY TIPS, your weekly connection with the most insightful tips and tricks that empower both newcomers and veterans in the Power Platform Community! Every Tuesday, we bring you a curated selection of the finest advice, distilled from the resources and tools in the Community. Whether you’re a seasoned member or just getting started, Tuesday Tips are the perfect compass guiding you across the dynamic landscape of the Power Platform Community.   To enhance our collaborative environment, it's important to acknowledge when your question has been answered satisfactorily. Here's a quick guide on how to accept a solution to your questions: Find the Helpful Reply: Navigate to the reply that has effectively answered your question.Accept as Solution: Look for the "Accept as Solution" button or link, usually located at the bottom of the reply.Confirm Your Selection: Clicking this button may prompt you for confirmation. Go ahead and confirm that this is indeed the solution.Acknowledgment: Once accepted, the reply will be highlighted, and the original post will be marked as "Solved". This helps other community members find the same solution quickly. By marking a reply as an accepted solution, you not only thank the person who helped you but also make it easier for others with similar questions to find answers. Let's continue to support each other by recognizing helpful contributions. 

Top Solution Authors
Top Kudoed Authors
Users online (5,661)