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:
"<hr width=1' size='" & ThisItem.MyHeight & "'>"(notice the single and double quotes in the above).
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.
Solved! Go to Solution.
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.
Hi @Anonymous,
Thank you for sharing your resolution here and hope that this would benefit anyone who has the similar situation.
Regards,
Mona
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.
@Anonymous could you please add a demo sir? i need this...
thank you
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.
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. 🙂
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
Episode Seven of Power Platform Connections sees David Warner and Hugo Bernier talk to Dian Taylor, alongside the latest news, product reviews, and community blogs. Use the hashtag #PowerPlatformConnects on social media for a chance to have your work featured on the show.
Super Users – 2023 Season 1 We are excited to kick off the Power Users Super User Program for 2023 - Season 1. The Power Platform Super Users have done an amazing job in keeping the Power Platform communities helpful, accurate and responsive. We would like to send these amazing folks a big THANK YOU for their efforts. Super User Season 1 | Contributions July 1, 2022 – December 31, 2022 Super User Season 2 | Contributions January 1, 2023 – June 30, 2023 Curious what a Super User is? Super Users are especially active community members who are eager to help others with their community questions. There are 2 Super User seasons in a year, and we monitor the community for new potential Super Users at the end of each season. Super Users are recognized in the community with both a rank name and icon next to their username, and a seasonal badge on their profile. Power Apps Power Automate Power Virtual Agents Power Pages Pstork1* Pstork1* Pstork1* OliverRodrigues BCBuizer Expiscornovus* Expiscornovus* ragavanrajan AhmedSalih grantjenkins renatoromao Mira_Ghaly* Mira_Ghaly* Sundeep_Malik* Sundeep_Malik* SudeepGhatakNZ* SudeepGhatakNZ* StretchFredrik* StretchFredrik* 365-Assist* 365-Assist* cha_cha ekarim2020 timl Hardesh15 iAm_ManCat annajhaveri SebS Rhiassuring LaurensM abm TheRobRush Ankesh_49 WiZey lbendlin Nogueira1306 Kaif_Siddique victorcp RobElliott dpoggemann srduval SBax CFernandes Roverandom schwibach Akser CraigStewart PowerRanger MichaelAnnis subsguts David_MA EricRegnier edgonzales zmansuri GeorgiosG ChrisPiasecki ryule AmDev fchopo phipps0218 tom_riha theapurva takolota Akash17 momlo BCLS776 Shuvam-rpa rampprakash ScottShearer Rusk ChristianAbata cchannon Koen5 a33ik Heartholme AaronKnox Matren Alex_10 Jeff_Thorpe poweractivate Ramole DianaBirkelbach DavidZoon AJ_Z PriyankaGeethik BrianS StalinPonnusamy HamidBee CNT Anonymous_Hippo Anchov KeithAtherton alaabitar Tolu_Victor KRider sperry1625 IPC_ahaas zuurg rubin_boer cwebb365 Dorrinda G1124 Gabibalaban Manan-Malhotra jcfDaniel WarrenBelz Waegemma If an * is at the end of a user's name this means they are a Multi Super User, in more than one community. Please note this is not the final list, as we are pending a few acceptances. Once they are received the list will be updated.
We are so excited to see you for the Microsoft Power Platform Conference in Las Vegas October 3-5 2023! But first, let's take a look back at some fun moments and the best community in tech from MPPC 2022 in Orlando, Florida. Featuring guest speakers such as Charles Lamanna, Heather Cook, Julie Strauss, Nirav Shah, Ryan Cunningham, Sangya Singh, Stephen Siciliano, Hugo Bernier and many more. Register today: https://www.powerplatformconf.com/
We are excited to share the ‘Power Platform Communities Front Door’ experience with you! Front Door brings together content from all the Power Platform communities into a single place for our community members, customers and low-code, no-code enthusiasts to learn, share and engage with peers, advocates, community program managers and our product team members. There are a host of features and new capabilities now available on Power Platform Communities Front Door to make content more discoverable for all power product community users which includes ForumsUser GroupsEventsCommunity highlightsCommunity by numbersLinks to all communities Users can see top discussions from across all the Power Platform communities and easily navigate to the latest or trending posts for further interaction. Additionally, they can filter to individual products as well. Users can filter and browse the user group events from all power platform products with feature parity to existing community user group experience and added filtering capabilities. Users can now explore user groups on the Power Platform Front Door landing page with capability to view all products in Power Platform. Explore Power Platform Communities Front Door today. Visit Power Platform Community Front door to easily navigate to the different product communities, view a roll up of user groups, events and forums.
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
User | Count |
---|---|
147 | |
99 | |
90 | |
76 | |
60 |
User | Count |
---|---|
247 | |
172 | |
116 | |
97 | |
92 |