Set Gallery Default Selected Item beyond the first 100 items

[kyasprin]

I have a Gallery populating from a delegable call to a Dataverse Table with over 100 items, so the Gallery will only load 100 items at a time as the user scrolls.

If I attempt to set the Default Selected Item to any of the first 100 items, it is selected as expected in the Gallery. But when I attempt to set the default item to anything beyond the 100th item, the Gallery can't select it b/c its not in view of the first 100 items. I've tried setting default selected manually to a Record like {ID:101}, w/ a variable or collection set somewhere else in the app like varSelectRecordID101 or colSelectRecordID101, w/ lookup to self: LookUp(Self.AllItems, ID = 101), or from form submissions like Form1.LastSubmit and all can only select a default item if its loaded in view within the Gallery.

If the Gallery is already scrolled down by the user to the point where the intended Default Selected Item is visible it gets selected, but I do not see an option to indicate the Gallery should automatically expand without user input and load the next 100 items at a time until it finds and can select the Default Selected item. This seems possible as Last(Self.AllItems) does exactly that to expand until it hits the very last record, then selects it (*Note* Last(<Datasource>) does not do this automatic expansion, only Self.AllItems).

Anyone know how to get around this without breaking the Delegable call to Dataverse or introducing Row Item Limits inside the app to load all of the data into the Gallery instead of 100 rows at a time?

Thanks in advance!

Edit: Updated Last(<Datasource>) to Last(Self.AllItems). Last(<Datasource>)  does NOT expand all items but Last(Self.AllItems) does.

[WarrenBelz]

Hi @kyasprin ,

Unfortunately you have a conundrum - the 100 record "batches" with any Delegable query is by design for performance reasons. As you would know, your Data Row Limit does not apply to Delegable queries (it is only for "client side" operations whereas a Delegable query is "server side") and the Default of a Gallery can only select from what it can "see" - the relevant record has not been given to it yet and it has no knowledge that it might be coming some time later.

I do not believe that you can achieve what you want here.

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.

MVP (Business Applications)   Visit my blog Practical Power Apps

[kyasprin]

Index() and Last() in the Default Item Selection property expand more than 100 items. Do these work b/c the data source recognizes them or is it built into power apps or those functions specifically to keep returning records until the desired record is visible in the Gallery?

[cwebb365]

So have you tried Lookup(SameasItemsDatasource,id= andIDPast100) as default selected? 

[WarrenBelz]

@kyasprin ,

I just did some testing here and (as expected) cannot get the Default to present past 100 items (without scrolling) using Last (simply does not work) Index (works up to 100, then does not) or LookUp (same as Index).

[kyasprin]

LookUp(<DataverseTable>, ID = <SomethingPast101>) and LookUp(Self.AllItems, ID = <SomethingPast101>) Both are limited to selecting from only the visible items in the Gallery. So initially only 100 items display for delegable calls to the Dataverse Table, so only the first 100 items can be set as the default. If user scrolls down to the bottom of the Gallery and the next 100 items loads, the Default from there can then be set to the first 200 items that are now displaying.

[kyasprin]

You are correct Last(<Datasource>) does not expand, but Last(Self.AllItems) does. Its interesting that Self.AllItems knows to continue pulling records automatically to expand and select the Default Item even if its beyond what is currently visible, but Last(<datasource>), Index(<Datasource or Self.AllItems>, ID = <SomethingAbove100>), or a Variable setting a record higher than displayed 100 items doesn't trigger the same expansion to pull more records until the selected item is visible.

I updated my original post to indicate Last(<Self.AllItems) does work but Last(<Datasource>) does not.

I'll have to keep pondering how I might be able to step around this and will post here if I can come up with something useful.

[cwebb365]

Last is non delegable so it’s having to return all records to get to it.  How large is this gallery supposed to get to? Seems like a UX issue to be scrolling so much to items? 

how many items can be in this gallery over time? If you just have to have a full gallery and it’ll always be under 2000 records then force a non delegable or use with / make a collection on load for it from your data source to pull the records local then use that as your items for the gallery. You can simple patch the collection right back to the data source with minimal effort patch(data source,collection) for updates.  

[trstrean · Accepted solution]

It seems like an easier approach is to give the user the ability to apply filters and reduce how much scrolling is necessary.  You could add a text search or some combo boxes that allow the user to filter things down and then the gallery would likely contain less than 100 items and avoid the issue 99% of the time.   Is there a reason why the user must scroll through more than 100 items where a filter wouldn't be desirable?

[kyasprin]

These datasources will likely grow beyond a couple thousand records. I was initially thinking of using the Default property to autoselect a newly added record from a form on the same screen as selecting the new record then has some other related functionality on the screen that would be nice to display automatically to the user after adding the new record. In addition to having this record auto selected display related content in other areas of the screen the user could see the item they just added selected and be able to scroll up and down in the Gallery from there to view/edit other items. But these aren't great options for resource utilization, especially as more and more of the Gallery would need loaded to autoselect.

I do have some text search and combo box filters that I had some initial hesitations on populating with the newly added record from the form with a variable, but I think this is the right way to go to retain delegable data calls in the Gallery while also selecting and displaying the newly added record to showcase the related content displayed on the page.

Thanks all!