Answered

Using SortByColumns and Filter on a table broke my subsequent table.selected references in forms

(0) Share

Report

Posted on by MatSeppanen

I have a table that users choose their item and then it opens a new screen drilling into the details. This works just fine, but then all of the Forms in lower level Screens no longer accept the table.Selected as the item that it is referencing and instead shows "no data"

SortByColumns(

AddColumns(

Filter (

Table,
txt_SearchList.Text in P1Request_ReportName
, ReportStatus in drop_StatusLookup.SelectedItems
,BP_Impact in drop_BPImpact.SelectedItems
),

"SortValue" , Priority.Value

"SortValue" , SortOrder.Ascending )

Without the Sort added, the filter works just fine and all the Forms function with Table.Selected. As soon as I add the Sort function it stops working. I am rather confused.

Categories:

Building Power Apps

I have the same question (0)

All responses (3)

Answers (1)

Sort by

Verified answer

BCBuizer 22,720 Super User 2026 Season 1 on at

Like (1)

Report
Copy link

Link copied!
Hi @MatSeppanen ,

Instead of referencing the Gallery.Selected property, try using it in a LookUp function to replace any references, for instance:

LookUp(Table, ID = Gallery.Selected.ID)

Was this reply helpful? Yes No
MatSeppanen 6 on at

Like (0)

Report
Copy link

Link copied!

wow... yep that did it thank you!

Was this reply helpful? Yes No
BCBuizer 22,720 Super User 2026 Season 1 on at

Like (0)

Report
Copy link

Link copied!

Hi @MatSeppanen ,

Usually it's the AddColumns function in the Items property of the gallery that causes this. Since this function changes the schema of the record, it is no longer recognised when Gallery.Selected is referenced. Using the LookUp function retrieves the record directly from the data source again, which has the original schema.

Was this reply helpful? Yes No