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

Flexible Height Gallery - a Better Way

 So the flexible height gallery control is very limited in usefulness out of the box.  The only controls with "auto height", which this functionality relies on, is the label control and HTML Text control.


I've seen some examples where people have used the Label control (making the text invisible) as a way to dynamically size each row (by adding more text in it), however, this was a bit quirky for me.  And now way to use this to really specify the height of the individual gallery item at a pixel level.

 

So I got to thinking that if the HTML Text control also works with Auto Size (it does), perhaps one could use this by using HTML to create a variable sized (to the pixel) vertical line.  


And yes, it works...  🙂  

 

Let's say your gallery is called Gallery1.  So what you would do is as follows:

 

  1. In Gallery1 add a column to what you have in Items, that will represent the height you want for each individual row.  I'll call this MyHeight for now.  So if I have 3 rows and want the first to be 10 pixels high, the second 20, and the third 30, I would just add these to the table. 

    There are other ways to do this (ie: value of a control within the gallery itself - ie: a slider that would allow the user to dynamically change it, resizing each row on the flow) - however, this depends on your usage.   

  2. Add an "HTML text" control to your gallery - I'll call this HtmlText1.  Set the following on HtmlText1:

    Auto height: ON  (IMPORTANT - and note I've seen PowerApps turn this off automatically sometimes, not sure why, so check it)
    X: 0
    Y: 0
    Width: 1
    Padding: Left: 0, Bottom: 0, Right: 0, Left: 0
    Height: Gallery1.TemplateHeight   (note: this could be any size you want to be the MINIMUM height, but setting it to this will allow you to drag the template size to this minimum)

  3. Now the "magic" here is in the HtmlText setting, so set HtmlText1.HtmlText to:

    "<hr width=1' size='" & ThisItem.MyHeight & "'>"
    (notice the single and double quotes in the above).

    This will create HTML to draw a vertical line 1 pixel wide and "ThisItem.MyHeight" pixels high.  Since the HtmlText1 control has Auto height On, the size of HTML 1 will change based on the length of the line.

    Note: Even though we set padding to 0, it appears that PowerApps will still make the height of the HtmlText1 control to itself be 5 pixels more than the length of the line.  Probably is a way around this, but doesn't matter to me.  

    Also note that there are many ways to specify the height of the line.  If you wanted to do this in a Slider that is within the gallery (letting the user set the individual slider to the size of that row), you could (instead of ThisItem.MyHeight) use ThisItem.Slider1.Value * 10 or something.

  4. And lastly, if you have a Separator line, say Separator1, you'd want to set its Y value to Max( HtmlText1.Height, Gallery1.TemplateHeight )

 

While this still is not a perfect substitute for the Gallery control not REALLY allowing for a flexible size (which it arguably SHOULD do) it does go a long way.  

Hope this helps someone.  If there is a better way to do this, please let me know, I'm very open to a better way.

 

1 ACCEPTED SOLUTION

Accepted Solutions
Anonymous
Not applicable

I'll try to post one for you.

Actually, with some of the changes in PowerApps, (there are still some issues with flexible height galleries), I had to change my approach, but what I've settled on seems to consistently work, regardless of the platform it was running on.  

With the other approach (posted above), I later discovered the sizing would be different depending on whether it was run as an app in Chrome/Chromium or Edge, whether it was running the web development environment, or if running on iOS or Android.  

 

I'm now using a rectangle object (either as a separator (height=1, Y=max height) or bounding rectangle (X=0, Y=0, height = max location of other controls) instead of the HTML.  This seems to work much better now.  I think the HTML approach differed between environments perhaps due to different assumptions those browsers/etc made about HTML spacing.  

To use the "bounding rectangle" approach, I set the X and Y of the rectangle to 0, and then for Height do something like the following:

Max( 
    If( 'FFG - CTRL TEXT INPUT'.Visible,         'FFG - CTRL TEXT INPUT'.Y         + 'FFG - CTRL TEXT INPUT'.Height,       0 ),
    If( 'FFG - CTRL DATE'.Visible,               'FFG - CTRL DATE'.Y               + 'FFG - CTRL DATE'.Height,             0 ),
    If( 'FFG - CTRL DATE RANGE START'.Visible,   'FFG - CTRL DATE RANGE START'.Y   + 'FFG - CTRL DATE RANGE START'.Height, 0 ),
    If( 'FFG - CTRL DROPDOWN'.Visible,           'FFG - CTRL DROPDOWN'.Y           + 'FFG - CTRL DROPDOWN'.Height,         0 ),
    If( 'FFG - CTRL COMBOBOX'.Visible,           'FFG - CTRL COMBOBOX'.Y           + 'FFG - CTRL COMBOBOX'.Height,         0 ), 
    If( 'FFG - CTRL CHECKBOX'.Visible,           'FFG - CTRL CHECKBOX'.Y           + 'FFG - CTRL CHECKBOX'.Height,         0 ),
    If( 'FFG - ERROR MSG Txt'.Visible,           'FFG - ERROR MSG Txt'.Y           + 'FFG - ERROR MSG Txt'.Height,         0 ),
    If( 'FFG - HEADER Txt'.Visible,              'FFG - HEADER Txt'.Y              + 'FFG - HEADER Txt'.Height,            0 ),
    If( 'FFG - textValue RESULT'.Visible,        'FFG - textValue RESULT'.Y        + 'FFG - textValue RESULT'.Height,      0 ), // Should only be visible if Debug is enabled
    /* Default */ 'FFG - NAME Txt'.Y + 'FFG - NAME Txt'.Height
) + 5

So in the above, my gallery is actually used to collect a user supplied range of filter criteria.  This is done in a custom control (FlexibleFilterGallery), I created, and the above is a snippet from it.  When using the control, it is passed in a table of "filter criteria" that specifies the type of control for the filter, the available values (for comboboxes, list boxes, drop downs), defaults, ranges (ie: start/end dates, numerical ranges, etc) that the control will use to provide the user the correct type of control, as well as limit options / validate user input.  

The template includes all those controls (combos, LBs, checkboxes, text entry, date, date range, etc), but only the one specified by the specific record in the table is set to Visible.

BTW - you'll also notice the check for the 'FFG - ERROR MSG Txt'.Visible.  This is only Visible if there was an error, and actually will increase the size of that cell to display the error message (ie: if for date range, end date is before start date) and once the error is corrected, the error message will then have Visible set to false, and thus the height of the cell will be reduced again automatically.

Thus, the code above with the If()s determine which one is visible, and then get its current Height - which depending on the control could be variable height (especially for text with autoheight set, etc).  

So this grabs the Max position from each of the Visible controls (in some other uses there might be multiple that are visible), adds 5 to this, and sets it to the height of the rectangle.  The flexible gallery control then correctly sizes itself, meaning that each record may be displayed in the gallery with a different height.

A slightly more complex way I use this is in a gallery or items (customer records) where each record may have multiple underlying records that I wish to display in the same template.  While I could do this with nested galleries (a gallery contained in a gallery), instead I'm using an HTML text field (with an HTML table) that is set to autoheight for the sub record.  (while this is not my specific use, consider this like a customer record, where perhaps the customer own multiple vehicles, so the "subrecord" is about the vehicles).  Initially the HTML is hidden, unless the user clicks on the "Show Details" button, which will then cause it to be set to Visible, and thus PowerApps will recalculate the size of that record in the template dynamically - expanding it as necessary.  You can show details of only the records you want which will only resize that one in the gallery accordingly.  Some have only 0, 1, or many subrecords (ie: vehicles in my example) - so the size will differ based on the record itself (number of rows as well as size of that row).  

Here I'm using the separator line approach (no difference in function, just visual appearance) with the HTML text set to autoheight.  So the Y for the separator (which is the bottom most control in the template) is:

If( 'AT - Usage Details Html_1'.Visible, 
    'AT - Usage Details Html_1'.Y + 'AT - Usage Details Html_1'.Height,
     'AT - Usage Details Html_1'.Y
)  + 5 


Works VERY well.  Sorry if the explanation was confusing - was typing this up between morning meetings (have to run for one).  Will see if I can post some screenshots later.

But hopefully the above gives you some ideas.


View solution in original post

6 REPLIES 6
v-monli-msft
Community Support
Community Support

Hi @Anonymous,

 

Thank you for sharing your resolution here and hope that this would benefit anyone who has the similar situation.

 

Regards,

Mona 

Community Support Team _ Mona Li
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
Anonymous
Not applicable

Thanks @v-monli-msft.  

BTW - I discovered today that this works differently when run in another "PowerApps Player" app - ie: "Windows Player" (the Windows store app), Android, and iOS vs the "Web Player" app that appears to be used when running from Studio or SharePoint.   

 

It appears that there are text and spacing issues when run across platforms.  I suspect that the way "pixels" are calculated within the HTML text control may vary between platforms.  I've seen similar things happen with text box placement, height etc between platforms, so believe this is related.

 

My workaround (as longer term this will need to work cross platform) will be to manually figure out a "scaling factor" for each player, and have the app apply that when its running (though there is no direct way to figure this out from PowerApps - I had to use an MS Flow that PowerApps calls and parse x-ms-user-agent to determine this from within my app).  If I get this part working in the near future, I'll update the post.  that said, I would suspect that this scaling might change in future versions of PowerApps as (hopefully) Microsoft brings the scaling across the different "players" closer together.  

 

 

PytByt
Post Prodigy
Post Prodigy

@Anonymous could you please add a demo sir? i need this...

thank you

Anonymous
Not applicable

I'll try to post one for you.

Actually, with some of the changes in PowerApps, (there are still some issues with flexible height galleries), I had to change my approach, but what I've settled on seems to consistently work, regardless of the platform it was running on.  

With the other approach (posted above), I later discovered the sizing would be different depending on whether it was run as an app in Chrome/Chromium or Edge, whether it was running the web development environment, or if running on iOS or Android.  

 

I'm now using a rectangle object (either as a separator (height=1, Y=max height) or bounding rectangle (X=0, Y=0, height = max location of other controls) instead of the HTML.  This seems to work much better now.  I think the HTML approach differed between environments perhaps due to different assumptions those browsers/etc made about HTML spacing.  

To use the "bounding rectangle" approach, I set the X and Y of the rectangle to 0, and then for Height do something like the following:

Max( 
    If( 'FFG - CTRL TEXT INPUT'.Visible,         'FFG - CTRL TEXT INPUT'.Y         + 'FFG - CTRL TEXT INPUT'.Height,       0 ),
    If( 'FFG - CTRL DATE'.Visible,               'FFG - CTRL DATE'.Y               + 'FFG - CTRL DATE'.Height,             0 ),
    If( 'FFG - CTRL DATE RANGE START'.Visible,   'FFG - CTRL DATE RANGE START'.Y   + 'FFG - CTRL DATE RANGE START'.Height, 0 ),
    If( 'FFG - CTRL DROPDOWN'.Visible,           'FFG - CTRL DROPDOWN'.Y           + 'FFG - CTRL DROPDOWN'.Height,         0 ),
    If( 'FFG - CTRL COMBOBOX'.Visible,           'FFG - CTRL COMBOBOX'.Y           + 'FFG - CTRL COMBOBOX'.Height,         0 ), 
    If( 'FFG - CTRL CHECKBOX'.Visible,           'FFG - CTRL CHECKBOX'.Y           + 'FFG - CTRL CHECKBOX'.Height,         0 ),
    If( 'FFG - ERROR MSG Txt'.Visible,           'FFG - ERROR MSG Txt'.Y           + 'FFG - ERROR MSG Txt'.Height,         0 ),
    If( 'FFG - HEADER Txt'.Visible,              'FFG - HEADER Txt'.Y              + 'FFG - HEADER Txt'.Height,            0 ),
    If( 'FFG - textValue RESULT'.Visible,        'FFG - textValue RESULT'.Y        + 'FFG - textValue RESULT'.Height,      0 ), // Should only be visible if Debug is enabled
    /* Default */ 'FFG - NAME Txt'.Y + 'FFG - NAME Txt'.Height
) + 5

So in the above, my gallery is actually used to collect a user supplied range of filter criteria.  This is done in a custom control (FlexibleFilterGallery), I created, and the above is a snippet from it.  When using the control, it is passed in a table of "filter criteria" that specifies the type of control for the filter, the available values (for comboboxes, list boxes, drop downs), defaults, ranges (ie: start/end dates, numerical ranges, etc) that the control will use to provide the user the correct type of control, as well as limit options / validate user input.  

The template includes all those controls (combos, LBs, checkboxes, text entry, date, date range, etc), but only the one specified by the specific record in the table is set to Visible.

BTW - you'll also notice the check for the 'FFG - ERROR MSG Txt'.Visible.  This is only Visible if there was an error, and actually will increase the size of that cell to display the error message (ie: if for date range, end date is before start date) and once the error is corrected, the error message will then have Visible set to false, and thus the height of the cell will be reduced again automatically.

Thus, the code above with the If()s determine which one is visible, and then get its current Height - which depending on the control could be variable height (especially for text with autoheight set, etc).  

So this grabs the Max position from each of the Visible controls (in some other uses there might be multiple that are visible), adds 5 to this, and sets it to the height of the rectangle.  The flexible gallery control then correctly sizes itself, meaning that each record may be displayed in the gallery with a different height.

A slightly more complex way I use this is in a gallery or items (customer records) where each record may have multiple underlying records that I wish to display in the same template.  While I could do this with nested galleries (a gallery contained in a gallery), instead I'm using an HTML text field (with an HTML table) that is set to autoheight for the sub record.  (while this is not my specific use, consider this like a customer record, where perhaps the customer own multiple vehicles, so the "subrecord" is about the vehicles).  Initially the HTML is hidden, unless the user clicks on the "Show Details" button, which will then cause it to be set to Visible, and thus PowerApps will recalculate the size of that record in the template dynamically - expanding it as necessary.  You can show details of only the records you want which will only resize that one in the gallery accordingly.  Some have only 0, 1, or many subrecords (ie: vehicles in my example) - so the size will differ based on the record itself (number of rows as well as size of that row).  

Here I'm using the separator line approach (no difference in function, just visual appearance) with the HTML text set to autoheight.  So the Y for the separator (which is the bottom most control in the template) is:

If( 'AT - Usage Details Html_1'.Visible, 
    'AT - Usage Details Html_1'.Y + 'AT - Usage Details Html_1'.Height,
     'AT - Usage Details Html_1'.Y
)  + 5 


Works VERY well.  Sorry if the explanation was confusing - was typing this up between morning meetings (have to run for one).  Will see if I can post some screenshots later.

But hopefully the above gives you some ideas.


jlucarelli
Regular Visitor

Thank you!  That worked like a charm for me.  And now that I know you can embed control properties in the HTML text control, I imagine I'll find other users for that as well.  🙂

anilrambhajan
Helper III
Helper III

Can someone help me. My gallery items are "cutting off" on different screen resolutions when I use the flexible height gallery with the visible property

Helpful resources

Announcements

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

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  

Copilot Cookbook Challenge | Week 1 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

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. 

Reminder: To register for the Community Ambassador Call on June 13th

Calling all Super Users & User Group Leaders     Reminder: To register for the Community Ambassador Call on June 13th—for an exclusive event for User Group Leaders and Super Users! This month is packed with exciting updates and activities within our community.   What's Happening: Community Updates: We'll share the latest developments and what's new in our vibrant community.Special Guest Speaker: Get ready for an insightful talk and live demo of Microsoft Copilot Studio templates by our special guest.Regular Updates: Stay informed with our routine updates for User Groups and Super Users.Community Insights: We'll provide general information about ongoing and upcoming community initiatives. Don't Miss Out: Register Now: Choose the session that fits your schedule best.Check your private messages or Super User Forum for registration links. We're excited to connect with you and continue building a stronger community together.   See you at the call!  

Top Solution Authors
Top Kudoed Authors
Users online (3,583)