In a model-driven app I have, one of my forms has an embedded QuickView form. The embedded form has a subgrid inside of it, and I expect that the subgrid will contain several rows of data (5+).
I have the subgrid set to "maximum 10 rows per page," which is working fine - pagination doesn't start until there are more than 10 rows of data. However, on the parent form, the embedded QuickView form is still only showing a few rows of data, and then you need to scroll within the QuickView to see more.
How can I change the shape of the QuickView form in the parent form, so that it is given more screen real estate?
I assume you're using the Unified interface, try adding that quick view form at the bottom of the tab/page, sometimes it auto expand to take the remaining height. Another thing to try is, if you're using make.powerapps.com to configure your quick view form (QVF), switch to classic interface, by opening the form in make.powerapps.com then click "Switch to classic" button. In classic, increase the number of rows of the subgrid:
@PowerAddict - The quickview form is in a tab with other items. Currently it's in a section with another item as well. It does have to stay in the tab it is in, but I could put it in a different section.
@EricRegnier I created the form in classic mode, and the number of rows in the subgrid is already set to 10. That seems to only control how many rows display on a page of the subgrid, not how much vertical space the quickview form will take up. There are enough other things on this form that "expand to fill available space" doesn't help, since there is less available space available than I need.
Yeah, the "Automatically expand to use available space" option is not supported yet in Unified interface. Just curious if you navigate to classic (remove the app param in the URL and add "&forceClassic=1 at the end"), do you get the expected behavior?
I would try to isolate the issue by, create a new basic form (one tab, one section), just like I did below. Add the lookup field then add the quick view form at the bottom.
I tried on my side and it works as expected see screenshot below:
I am doing all of this editing in classic mode because I know it doesn't work in the new interface.
As far as I understand, "expand to use available space" will do what it says. Everything else on the page gets rendered, and then the control with "available space" set will go into the space that is left. If what is left is three rows tall, that's the available space, and you will see three rows with a scrollbar. This is not the behavior I want. If the control is set to display 10 rows on a page, I want to have all 10 rows displayed with no scrollbar on the control, just the scrollbar on the window.
One of the other issues is that this form is intended to display on a Powerapps Portal. I've noticed that some of the display options work fine when I view them in a model-driven app, but don't display the expected way in the Portal.
Keep up to date with current events and community announcements in the Power Apps community.
A great place where you can stay up to date with community calls and interact with the speakers.
Check out the latest Community Blog from the community!