Applying model driven filtering to related virtual table doesn't work.

(0) Share

Report

Posted on by Emejcz

Hello.

What I am trying to achieve is prepare fetchXML to use in preSearch lookup filtering.

I have systemuser table with lookup column to virtual table.

I would like to set lookup filtering where it shows records from systemuser table where related to virtual table rows meet requirements like have some specific name or ID.

Filtering looks more or less like this:

The issue with this filtering is that NONE of rows from virtual table have name eq TestName and it still displays all available rows while it should display none.

It happens also with other columns.

When I apply such filtering to another related table that is not virtual it works exactly as expected so it looks like it is something wrong with filtering to virtual table.

Any ideas on this one?

I found some info from last year stating some issues with AAD Table and lookup search and started wondering if there is also some bug in my case...

Categories:

Building Power Apps

I have the same question (0)

All responses (2)

Answers (0)

Sort by

Linn Zaw Win 2,996 on at

Like
a
(2)

Report
Copy link

Link copied!

This is what I found in the limitations of virtual tables.
"Although you can add virtual table columns as a lookup on a grid or other UI views, you cannot filter or sort based on this virtual table lookup column."
https://learn.microsoft.com/en-us/power-apps/developer/data-platform/virtual-entities/get-started-ve

Was this reply helpful? Yes No
Linn Zaw Win 2,996 on at

Like
a
(0)

Report
Copy link

Link copied!

@Emejcz
Even though there is no solution for it but if my reply answers your question, can you please mark it as a solution to close this thread? That will be useful for others in the community who come across this thread to identify the solution easily.

Was this reply helpful? Yes No