Using "in" operator in Filter function for binding drop down based on two tables

(0) Share

Report

Posted on by ereyaz

Hi Team,

I am using Azuer SQL server and power apps.

I am binding a dropdown with below formula for showing Account Name based on two tables where account table contain accountid, accountname and accountaccess table contain accountid and userid:

Filter('[dbo].[Account]', AccountID in Filter('[dbo].[AccountAccess]', UserID = LoggedUser).AccountID)

Currently both tables contain few records so its binding correctly but when it will crossed beyond 500-2000(limitation of delegable) then it will not bind all data waht i read on delegable function for below messege on blue line of "in" operator.

"Part of this formula cannot be evaluated remotely. right side of "in" operator is not a column name"

So can any one suggest how it will resolve the issue if tables contain 50,000 records or more.

Thanksa and Regards,

Reyaz

Categories:

Building Power Apps

I have the same question (0)

All responses (3)

Answers (1)

Verified answer

timl 36,415 Super User 2025 Season 2 on at

Like (0)

Report
Hi Reyaz

To overcome the delegation problem, I would recoomend that you create a view in SQL Server. You can then bind your dropdown to this view to overcome the delegation limit.

The view would look something like this...

CREATE VIEW [dbo].[AccountAccessView] AS SELECT Distinct ac.AccountName, aa.AccountID, aa.UserID FROM [dbo].[Account] ac JOIN [dbo].[AccountAccess] aa ON ac.AccountID = aa.AccountID

The formula that you would use for your dropdown should hopefully avoid the delegation problem.

Filter([dbo].[AccountAccessView] , UserID=LoggedUser)

Was this reply helpful? Yes No
ereyaz 18 on at

Like (0)

Report

Thank you so much for the quick solution.

Thanks and Regards,
Reyaz

Was this reply helpful? Yes No
timl 36,415 Super User 2025 Season 2 on at

Like (0)

Report

Sure, you're welcome!

Was this reply helpful? Yes No