Refresh Datasource displays first row in Sharepoint List

[Nav12]

Hi All,

This is ongoing work from the following question I had : Solved: Re: Showing newly updated field in Sharepoint list... - Page 2 - Power Platform Community (m...

I followed the advice given and it works - however, I really want to be able to 'Search' on the Gallery (connected to a datasource) which is a SharePoint List.

Situation:

Gallery1 on Screen1.

Items: Search('CloudTasks', SearchBox.Text, "TaskName", "Client")

OnSelect: Navigate('Detailed', Fade)

(Detailed is on screen2 and shows more fields)

Gallery2 on Screen2 (which is  the Detailed info regarding the info within Gallery1)..it is pointing to the same data source of CloudTasks.

Items: Table(Gallery1.Seclected)

I am patching a field within CloudTasks (SharePoint list) from within a Power Automate.

I then want to refresh a label which is the patched value.

So - I have a button which has:

OnSelect: Refresh ('CloudTasks').

Now, if I have this:

Gallery1 on Screen1.

Items: 'CloudTasks'

The refresh button works perfectly and displays my patched record and the remaining items within Gallery2 are all correct to.

But - if I want my Search functionality - which I do...my Gallery1 is this:

Gallery1 on Screen1.

Items: Search('CloudTasks', SearchBox.Text, "TaskName", "Client")

When I have this and I hit my refresh button - what it does is refresh and if I have selected row 2 (any row) for example - the Gallery2 on Screen2 displays the first row data in my SharePoint list. It always displays the first row - no matter which record I have selected to drill into....

Why is it defaulting the results to the first row ... no matter which record I am on and trying to refresh?

Thanks.

[RandyHayes]

@Nav12 

This is a side effect of the Refresh in conjunction with Gallery selection.

If your Items formula is a simple formula, your current selection will remain.  However, in your case, the formula is considered "complex" because it is an evaluated formula - meaning that the Search function determines the resultant table for the gallery.  So, when the core datasource is refreshed, the Gallery will re-evaluate the formula and your selection will change.

One way you can combat this is to take a snapshot of the selected record at the time of selection.

So, in your OnSelect action of Gallery1, change the formula to:

   UpdateContext({lclSelectedRecord: ThisItem}); Navigate('Detailed', Fade)

Then set the Default property of Gallery1 to the following formula:

   lclSelectRecord

This will force the default back to the originally selected record.  If there are no complex columns in the record that could cause the matching to fail, then this will work for you.

I hope this is helpful for you.

[Nav12]

 Thanks @RandyHayes .

I added in your edits as above.

Now... when I hit my Refresh button ... it wipes out all the fields (i.e blanks all Gallery2...where before it went to row 1)

If I go back to screen 1 and then into screen 2 again - my data is back....

[Nav12]

Sorry @RandyHayes - it is not wiping out the records...my mistake.

However, the behaviour is the same....it still refreshes to row 1.

So no difference.

[RandyHayes]

@Nav12 

So, matching a default for a Gallery is sometimes a challenge.  There are a variety of columns from the SharePoint list that can potentially interfere with the matching.

First...let's make one slight alteration on the last post I sent.  Set the OnSelect formula to the following:

UpdateContext({lclSelectedRecord: LookUp(CloudTasks, ID=ThisItem.ID}); Navigate('Detailed', Fade)

If that does not resolve it, then we need to start to do some stripping of columns from your Gallery.

[Nav12]

Thanks @RandyHayes ... it is actually wiping out the record (it was inconsistent the first time -which is why I pulled back my original post about the wiping). Though I like your thinking with going after the ID of the SP List record...i though that would be it...

I think i'll live without the Search capability based on your 'side effects' statement above.

Thanks for all your help though.

[RandyHayes]

@Nav12 

Okay, before throwing in the towel...

Set the OnSelect to:  UpdateContext({lclSelectedRecord: ThisItem.ID}); Navigate('Detailed', Fade)

Then the Default to : LookUp(CloudTasks, ID=lclSelectedRecord)

If that's a no-go, then yes, you could stick with the side effect, but if you ever want to tackle it, what really needs to be done is to strip down the Items property of the Gallery to supply only the columns you want. 

So, for example, if you have a Title and a Description showing in your Gallery, then you would set the Items property of the Gallery to :  ShowColumns(dataSource, "ID", "Title", "Description")

The OnSelect can be one of a couple things, either set the variable to the ID of the current record (if you feel that the Title or Description will change somewhere else in your app), or set the variable to the record ID just like above.

THEN, the Default property would be:  LookUp(ShowColumns(CloudTasks, ID=lclSelectedRecord), "ID", "Title", "Description")

Those would definitely work.  They may have other side effects depending on any dependencies you have in the App for the selected record of the Gallery, but those are easy to work around.

[Nav12]

Thanks @RandyHayes - will test this out in the morning (I'm in the UK :)).

Thanks for your help thus far...much appreciated.

[RandyHayes]

@Nav12 

Anytime!  Happy to help!  Have a great evening.