cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
jbrit2020
Continued Contributor
Continued Contributor

Auto Width of any controls

So, after spending days scratching my head on how to make a label width adjustable, and extremely unhappy with the formula:

 

 

 

 

 

20*Len(Label1.Text)

 

 

 

 

That increases the size, but doesn't really match THE size of the text (the label can end up being 4 or 5 times the size of the text)

 

I started fiddling with Point conversions and came up with this formula. You don't need to change the 0.352777777778 value as that is the average point value in millimetres of font size systems:

 

 

 

 

 

Max(25,((Label1.Size+(0.35277777777778*Label1.Size))*Len(Label1.Text))-((0.35277777777778*Len(Label1.Text))*(Len(Label1.Text))))

 

 

 

 

 

Doesn't look pretty, and probably have one too many () in there, but it seems to work wonders for me as it matches NEARLY perfectly the width of the TEXT.

 

I'm just posting it here because it seems to be a common question and thought someone could make use of this or hopefully even, improve the formula to be slicker.

 

Please do test and let me know if it works for you as well.

1 ACCEPTED SOLUTION

Accepted Solutions

@jbrit2020 
The best way to make an auto-width label is:

  • Place an HTML control on the canvas with the same font, font size and font weight
  • Set the Auto-Height property to true
  • Rotate text 90 degrees using CSS
  • Make the label width equal to the height of the HTML control

 

I show all the steps to do it in this tutorial:
https://www.matthewdevaney.com/how-to-make-a-power-apps-auto-width-label/

SSAEDW_0-1674423706965.jpeg

 

View solution in original post

10 REPLIES 10
Rohit_RC
Frequent Visitor

Hi @jbrit2020 , you can use auto-height property of Text label control, it will auto increase the height based on the length of text entered

Lexicon_320
Regular Visitor

This didn't work for me. I assume it's meant to go in the Width property since we're trying to auto-width our labels to match its contents. I changed all the Label1 references to Self.

 

 

 

Max(25, ((Self.Size+(0.35277777777778*Self.Size))*Len(Self.Text))-((0.35277777777778*Len(Self.Text))*(Len(Self.Text))))

 

 

 

My label at font size 10, length 41 requires a width of 230 to fit all the text in one line, but the formula maxes out at 25 because the second part calculates to a negative number (-38).

 

Yet another one (font size 12, length 73) requiring a width of 567 calculated to -695.

 

Have I severely misunderstood this post?

Anonymous
Not applicable

Works just perfectly!! Thank you 🙂

SSAEDW
Regular Visitor

 

...

 

@jbrit2020 
The best way to make an auto-width label is:

  • Place an HTML control on the canvas with the same font, font size and font weight
  • Set the Auto-Height property to true
  • Rotate text 90 degrees using CSS
  • Make the label width equal to the height of the HTML control

 

I show all the steps to do it in this tutorial:
https://www.matthewdevaney.com/how-to-make-a-power-apps-auto-width-label/

SSAEDW_0-1674423706965.jpeg

 

Anonymous
Not applicable

This worked for me: 
1. Select the label you would like to auto-width

2. Go to the toolbar for this element

3. Find Width in the dropdown

4. Enter this  Value(Len(Self.Text)*14)

You can adjust the number 14 to any number depending on the width of your font.

DouglasY
Frequent Visitor

Here's a workaround I came up with that is pretty accurate. Just copy and paste this formula into the Width of the label you want to auto-size. Unfortunately though, this specifically only works with the following conditions (still working on a way to include all the extra variables):

*Only includes the 95 characters found on a keyboard
*font-type: 'Open Sans'

*font-weight: Normal

*font-style: none

 

(RoundUp(
  ((CountRows(MatchAll(Self.Text, "m"))
  +CountRows(MatchAll(Self.Text, "M"))
  +CountRows(MatchAll(Self.Text, "W")))
  *(Self.Size-(Self.Size*-0.25))) //m,M,W
  +
  ((CountRows(MatchAll(Self.Text, "\@"))
  *(Self.Size-(Self.Size*-0.2)))) //@
  +
  ((CountRows(MatchAll(Self.Text, "N"))
  +CountRows(MatchAll(Self.Text, "O"))
  +CountRows(MatchAll(Self.Text, "Q")))
  *(Self.Size-(Self.Size*-0.05))) //N,0,Q
  +
  ((CountRows(MatchAll(Self.Text, "\%"))
  *(Self.Size-(Self.Size*-0.1)))) //%
  +
  ((CountRows(MatchAll(Self.Text, "D"))
  +CountRows(MatchAll(Self.Text, "G"))
  +CountRows(MatchAll(Self.Text, "H"))
  +CountRows(MatchAll(Self.Text, "U"))
  +CountRows(MatchAll(Self.Text, "\&")))
  *(Self.Size-(Self.Size*0))) //D,G,H,U,&
  +
  ((CountRows(MatchAll(Self.Text, "w"))
  *(Self.Size-(Self.Size*0.05)))) //w
  +
  ((CountRows(MatchAll(Self.Text, "B"))
  +CountRows(MatchAll(Self.Text, "\#")))
  *(Self.Size-(Self.Size*0.1))) //B,#
  +
  ((CountRows(MatchAll(Self.Text, "b"))
  +CountRows(MatchAll(Self.Text, "d"))
  +CountRows(MatchAll(Self.Text, "h"))
  +CountRows(MatchAll(Self.Text, "n"))
  +CountRows(MatchAll(Self.Text, "o"))
  +CountRows(MatchAll(Self.Text, "p"))
  +CountRows(MatchAll(Self.Text, "q"))
  +CountRows(MatchAll(Self.Text, "u"))
  +CountRows(MatchAll(Self.Text, "A"))
  +CountRows(MatchAll(Self.Text, "C"))
  +CountRows(MatchAll(Self.Text, "K"))
  +CountRows(MatchAll(Self.Text, "P"))
  +CountRows(MatchAll(Self.Text, "R")))
  *(Self.Size-(Self.Size*0.15))) //b,d,h,n,o,p,q,u,A,C,K,P,R
  +
  ((CountRows(MatchAll(Self.Text, "V"))
  +CountRows(MatchAll(Self.Text, "X"))
  +CountRows(MatchAll(Self.Text, "Z"))
  +CountRows(MatchAll(Self.Text, "0"))
  +CountRows(MatchAll(Self.Text, "1"))
  +CountRows(MatchAll(Self.Text, "2"))
  +CountRows(MatchAll(Self.Text, "3"))
  +CountRows(MatchAll(Self.Text, "4"))
  +CountRows(MatchAll(Self.Text, "5"))
  +CountRows(MatchAll(Self.Text, "6"))
  +CountRows(MatchAll(Self.Text, "7"))
  +CountRows(MatchAll(Self.Text, "8"))
  +CountRows(MatchAll(Self.Text, "9"))
  +CountRows(MatchAll(Self.Text, "\~"))
  +CountRows(MatchAll(Self.Text, "\$"))
  +CountRows(MatchAll(Self.Text, "\+"))
  +CountRows(MatchAll(Self.Text, "\="))
  +CountRows(MatchAll(Self.Text, "\<"))
  +CountRows(MatchAll(Self.Text, "\>")))
  *(Self.Size-(Self.Size*0.2))) //V,X,Z,0,1,2,3,4,5,6,7,8,9,~,`,$,+,=,<,>
  +
  ((CountRows(MatchAll(Self.Text, "a"))
  +CountRows(MatchAll(Self.Text, "e"))
  +CountRows(MatchAll(Self.Text, "g"))
  +CountRows(MatchAll(Self.Text, "E"))
  +CountRows(MatchAll(Self.Text, "S"))
  +CountRows(MatchAll(Self.Text, "T"))
  +CountRows(MatchAll(Self.Text, "Y"))
  +CountRows(MatchAll(Self.Text, "\^"))
  +CountRows(MatchAll(Self.Text, "\*"))
  +CountRows(MatchAll(Self.Text, "\|")))
  *(Self.Size-(Self.Size*0.25))) //a,e,g,E,S,T,Y,^,*,|
  +
  ((CountRows(MatchAll(Self.Text, "k"))
  +CountRows(MatchAll(Self.Text, "v"))
  +CountRows(MatchAll(Self.Text, "x"))
  +CountRows(MatchAll(Self.Text, "y"))
  +CountRows(MatchAll(Self.Text, "F"))
  +CountRows(MatchAll(Self.Text, "L")))
  *(Self.Size-(Self.Size*0.3))) //k,v,x,y,F,L
  +
  ((CountRows(MatchAll(Self.Text, "c"))
  +CountRows(MatchAll(Self.Text, "s"))
  +CountRows(MatchAll(Self.Text, "z")))
  *(Self.Size-(Self.Size*0.35))) //c,s,z
  +
  ((CountRows(MatchAll(Self.Text, "_"))
  +CountRows(MatchAll(Self.Text, "\?")))
  *(Self.Size-(Self.Size*0.35))) //_,?
  +
  ((CountRows(MatchAll(Self.Text, "r"))
  +CountRows(MatchAll(Self.Text, "\{"))
  +CountRows(MatchAll(Self.Text, "\}"))
  +CountRows(MatchAll(Self.Text, "\""")))
  *(Self.Size-(Self.Size*0.45))) //r,{,},"
  +
  ((CountRows(MatchAll(Self.Text, "f"))
  +CountRows(MatchAll(Self.Text, "t"))
  +CountRows(MatchAll(Self.Text, "\\"))
  +CountRows(MatchAll(Self.Text, "\/")))
  *(Self.Size-(Self.Size*0.5))) //f,t,\,/
  +
  ((CountRows(MatchAll(Self.Text, "\-"))
  +CountRows(MatchAll(Self.Text, "\["))
  +CountRows(MatchAll(Self.Text, "\]")))
  *(Self.Size-(Self.Size*0.55))) //-,[,]
  +
  ((CountRows(MatchAll(Self.Text, "I"))
  +CountRows(MatchAll(Self.Text, "J"))
  +CountRows(MatchAll(Self.Text, "\!"))
  +CountRows(MatchAll(Self.Text, "\("))
  +CountRows(MatchAll(Self.Text, "\)"))
  +CountRows(MatchAll(Self.Text, "\:"))
  +CountRows(MatchAll(Self.Text, "\;"))
  +CountRows(MatchAll(Self.Text, "\.")))
  *(Self.Size-(Self.Size*0.6))) //I,J,!,(,),:,;,.,,,`
  +
  ((CountRows(MatchAll(Self.Text, "i"))
  +CountRows(MatchAll(Self.Text, "j"))
  +CountRows(MatchAll(Self.Text, "l"))
  +CountRows(MatchAll(Self.Text, " "))
  +CountRows(MatchAll(Self.Text, "\,")))
  *(Self.Size-(Self.Size*0.65))) //i,j,l,,
  +
  ((CountRows(MatchAll(Self.Text, "\'")))
  *(Self.Size-(Self.Size*0.7)))
  , 0))

For bigger applications this would add an unnecessary control. I think a math solution is perfect. 

 

Since this post have you seen any other solutions?


Please click Accept as solution if my post helped you solve your issue. This will help others find it more readily. It also closes the item. If the content was useful in other ways, please consider giving it Thumbs Up.

Super User since Season 1 2023

Coach Ky -
SanSha
New Member

Following worked for me for auto-width with font size accounted for. Tested only with labels and on PC, please confirm with other controls and devices

Len(Self.Text)*(Self.Size * 0.7)

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!

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.    

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

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  

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 (3,859)