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

@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

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

@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 🙂

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

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