Answered

Gallery Filter on Lookup using the .Id field is not working, but works when using the .Value field

(0) Share

Report

Posted on by JWolmanSymplr

I build several power apps based on SharePoint lists and I am running into an odd issue with one of my Power Apps.

I have a landing page that lists out all records from my list of Components. When you select a Component I navigate to a different new page that has the details of the record I selected and I have another Gallery that I am filtering out a different SharePoint list because this is a parent/child relationship. The child has a field that is a look to the parent. In my case "Component Name"

I am seeing odd behavior on my Items method using the Sort Filter logic I have used in many of my other Power Apps.

Sort(Filter([@'Innovation Components Versions'], 'Component Name'.Id = BrowseGallery.Selected.ID),'Product Name'.Value,SortOrder.Ascending)

Is not working. The Child records are not showing. BrowseGallery is my Parent list, and Component Name is my lookup field on the Child list.

If I change this to be:

Sort(Filter([@'Innovation Components Versions'], 'Component Name'.Value = BrowseGallery.Selected.'Name (Title)'),'Product Name'.Value,SortOrder.Ascending)

Then my Child records are showing.

Why would it not work when I am searching directly for the Id value? Even when I change the BrowseGalllery.Selected.ID to be the exact value of the Parent lookup (134) it still does not work.

The other strange part of this is, if I change the hard coded Id value to a lower value like 13, then it works. It seems like it will not filter an ID that is above 128. But the records all exist.

Categories:

Building Power Apps

Components Power ...

I have the same question (0)

All responses (4)

Answers (1)

jadhav_ravi_oo7 276 on at

Like (0)

Report

brother we have to convert text to number then it will match and give you result like this-

Sort(Filter([@'Innovation Components Versions'], value( 'Component Name'.Id) = value(BrowseGallery.Selected.ID)),'Product Name'.Value,SortOrder.Ascending)

kindly like the post if i provided correct ans ->

Thanks & Regards,
Ravindra Jadhav
Independent Consultant | Freelancer
Connect Me On Different Platforms
LinkedIn || YouTube ||Blogger ||

Was this reply helpful? Yes No
JWolmanSymplr 24 on at

Like (0)

Report

That did not work in my case. Again if I use a different Parent record that was created several weeks ago the child gallery works just fine. It's not working with any new Parent records I created yesterday or today.

This works if BrowseGallery.Selected.ID = 128 (or less). Does not work for my new BrowseGallery.Selected.ID of 134 (which the record was created yesterday.

Sort(Filter([@'Innovation Components Versions'], 'Component Name'.Id = BrowseGallery.Selected.ID),'Product Name'.Value,SortOrder.Ascending)

Was this reply helpful? Yes No
Verified answer

jadhav_ravi_oo7 276 on at

Like (0)

Report

brother Because of delegation up to 128 it is working properly after that it is giving error because of delegation limit of power apps.

Was this reply helpful? Yes No
JWolmanSymplr 24 on at

Like (0)

Report

Ah, the Settings > General > Data row limit. It was still at 200, I changed to 2000.

However, why does it work when I change the filter to use "'Component Name'.Value = BrowseGallery.Selected.'Name (Title)'" it works? But not when I used "'Component Name'.Id = BrowseGallery.Selected.ID"?

This makes no sense to me unless there is some built in magic in SharePoint when using the .Id/.ID fields it's being limited and not when using the .Value/.Name fields?

Was this reply helpful? Yes No