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

Check out the Copilot Studio Cookbook today!

We are excited to announce our new Copilot Cookbook Gallery in the Copilot Studio Community. We can't wait for you to share your expertise and your experience!    Join us for an amazing opportunity where you'll be one of the first to contribute to the Copilot Cookbook—your ultimate guide to mastering Microsoft Copilot. Whether you're seeking inspiration or grappling with a challenge while crafting apps, you probably already know that Copilot Cookbook is your reliable assistant, offering a wealth of tips and tricks at your fingertips--and we want you to add your expertise. What can you "cook" up?   Click this link to get started: https://aka.ms/CS_Copilot_Cookbook_Gallery   Don't miss out on this exclusive opportunity to be one of the first in the Community to share your app creation journey with Copilot. We'll be announcing a Cookbook Challenge very soon and want to make sure you one of the first "cooks" in the kitchen.   Don't miss your moment--start submitting in the Copilot Cookbook Gallery today!     Thank you,  Engagement Team

Announcing Power Apps Copilot Cookbook Gallery

We are excited to share that the all-new Copilot Cookbook Gallery for Power Apps is now available in the Power Apps Community, full of tips and tricks on how to best use Microsoft Copilot as you develop and create in Power Apps. The new Copilot Cookbook is your go-to resource when you need inspiration--or when you're stuck--and aren't sure how to best partner with Copilot while creating apps.   Whether you're looking for the best prompts or just want to know about responsible AI use, visit Copilot Cookbook for regular updates you can rely on--while also serving up some of your greatest tips and tricks for the Community. Check Out the new Copilot Cookbook for Power Apps today: Copilot Cookbook - Power Platform Community.  We can't wait to see what you "cook" up!      

Tuesday Tip | How to Report Spam in Our Community

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.   As our community family expands each week, we revisit our essential tools, tips, and tricks to ensure you’re well-versed in the community’s pulse. Keep an eye on the News & Announcements for your weekly Tuesday Tips—you never know what you may learn!   Today's Tip: How to Report Spam in Our Community We strive to maintain a professional and helpful community, and part of that effort involves keeping our platform free of spam. If you encounter a post that you believe is spam, please follow these steps to report it: Locate the Post: Find the post in question within the community.Kebab Menu: Click on the "Kebab" menu | 3 Dots, on the top right of the post.Report Inappropriate Content: Select "Report Inappropriate Content" from the menu.Submit Report: Fill out any necessary details on the form and submit your report.   Our community team will review the report and take appropriate action to ensure our community remains a valuable resource for everyone.   Thank you for helping us keep the community clean and useful!

Community Roundup: A Look Back at Our Last 10 Tuesday Tips

As we continue to grow and learn together, it's important to reflect on the valuable insights we've shared. For today's #TuesdayTip, we're excited to take a moment to look back at the last 10 tips we've shared in case you missed any or want to revisit them. Thanks for your incredible support for this series--we're so glad it was able to help so many of you navigate your community experience!   Getting Started in the Community An overview of everything you need to know about navigating the community on one page!  Community Links: ○ Power Apps ○ Power Automate  ○ Power Pages  ○ Copilot Studio    Community Ranks and YOU Have you ever wondered how your fellow community members ascend the ranks within our community? We explain everything about ranks and how to achieve points so you can climb up in the rankings! Community Links: ○ Power Apps ○ Power Automate  ○ Power Pages  ○ Copilot Studio    Powering Up Your Community Profile Your Community User Profile is how the Community knows you--so it's essential that it works the way you need it to! From changing your username to updating contact information, this Knowledge Base Article is your best resource for powering up your profile. Community Links: ○ Power Apps ○ Power Automate  ○ Power Pages  ○ Copilot Studio    Community Blogs--A Great Place to Start There's so much you'll discover in the Community Blogs, and we hope you'll check them out today!  Community Links: ○ Power Apps ○ Power Automate  ○ Power Pages  ○ Copilot Studio    Unlocking Community Achievements and Earning Badges Across the Communities, you'll see badges on users profile that recognize and reward their engagement and contributions. Check out some details on Community badges--and find out more in the detailed link at the end of the article! Community Links: ○ Power Apps  ○ Power Automate  ○ Power Pages  ○ Copilot Studio    Blogging in the Community Interested in blogging? Everything you need to know on writing blogs in our four communities! Get started blogging across the Power Platform communities today! Community Links: ○ Power Apps  ○ Power Automate  ○ Power Pages  ○ Copilot Studio   Subscriptions & Notifications We don't want you to miss a thing in the community! Read all about how to subscribe to sections of our forums and how to setup your notifications! Community Links: ○ Power Apps  ○ Power Automate  ○ Power Pages  ○ Copilot Studio   Getting Started with Private Messages & Macros Do you want to enhance your communication in the Community and streamline your interactions? One of the best ways to do this is to ensure you are using Private Messaging--and the ever-handy macros that are available to you as a Community member! Community Links: ○ Power Apps  ○ Power Automate  ○ Power Pages  ○ Copilot Studio   Community User Groups Learn everything about being part of, starting, or leading a User Group in the Power Platform Community. Community Links: ○ Power Apps  ○ Power Automate  ○ Power Pages  ○ Copilot Studio   Update Your Community Profile Today! Keep your community profile up to date which is essential for staying connected and engaged with the community. Community Links: ○ Power Apps  ○ Power Automate  ○ Power Pages  ○ Copilot Studio   Thank you for being an integral part of our journey.   Here's to many more Tuesday Tips as we pave the way for a brighter, more connected future! As always, watch the News & Announcements for the next set of tips, coming soon!

Hear what's next for the Power Up Program

Hear from Principal Program Manager, Dimpi Gandhi, to discover the latest enhancements to the Microsoft #PowerUpProgram, including a new accelerated video-based curriculum crafted with the expertise of Microsoft MVPs, Rory Neary and Charlie Phipps-Bennett. If you’d like to hear what’s coming next, click the link below to sign up today! https://aka.ms/PowerUp  

Welcome to the Power Apps Community

Welcome! Congratulations on joining the Microsoft Power Apps community! You are now a part of a vibrant group of peers and industry experts who are here to network, share knowledge, and even have a little fun! Now that you are a member, you can enjoy the following resources:   The Microsoft Power Apps Community Forums If you are looking for support with any part of Microsoft Power Apps, our forums are the place to go. They are titled "Get Help with Microsoft Power Apps " and there you will find thousands of technical professionals with years of experience who are ready and eager to answer your questions. You now have the ability to post, reply and give "kudos" on the Power Apps community forums! Make sure you conduct a quick search before creating a new post because your question may have already been asked and answered!   Microsoft Power Apps IdeasDo you have an idea to improve the Microsoft Power Apps experience, or a feature request for future product updates? Then the "Power Apps Ideas" section is where you can contribute your suggestions and vote for ideas posted by other community members. We constantly look to the most voted Ideas when planning updates, so your suggestions and votes will always make a difference.   Community Blog & NewsOver the years, more than 600 Power Apps Community Blog Articles have been written and published by our thriving community. Our community members have learned some excellent tips and have keen insights on building Power Apps. On the Power Apps Community Blog, read the latest Power Apps related posts from our community blog authors around the world. Let us know if you would like to become an author and contribute your own writing — everything Power Apps related is welcome!   Power Apps Samples, Learning and Videos GalleriesOur galleries have a little bit of everything to do with Power Apps. Our galleries are great for finding inspiration for your next app or component. You can view, comment and kudo the apps and component gallery to see what others have created! Or share Power Apps that you have created with other Power Apps enthusiasts. Along with all of that awesome content, there is the Power Apps Community Video & MBAS gallery where you can watch tutorials and demos by Microsoft staff, partners, and community gurus in our community video gallery.   Again, we are excited to welcome you to the Microsoft Power Apps community family! Whether you are brand new to the world of process automation or you are a seasoned Power Apps veteran. Our goal is to shape the community to be your ‘go to’ for support, networking, education, inspiration and encouragement as we enjoy this adventure together!   Let us know in the Community Feedback if you have any questions or comments about your community experience.To learn more about the community and your account be sure to visit our Community Support Area boards to learn more! We look forward to seeing you in the Power Apps Community!The Power Apps Team

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