Unanswered

Unable to filter a Dataverse table view on a column that uses AAD Users virtual table

(0) Share

Report

Posted on by JR-15081603-0

I have created a lookup column in my table that uses AAD Users as the lookup choices. This works perfectly in a form and when displaying data in a view. However, I'd like to be able to filter a view when that lookup column value is equal to me. When trying to create a view filter on that column, I receive the following error: We are having trouble getting data for the filters. Please try again.

Having a lookup column like this is a great idea. However, if I can't filter on it, then what's the point? It's likely that I am missing something simple. Or can we just not filter on the data since it's from a virtual table.

Thanks in advance.

Categories:

Microsoft Dataverse with Power Apps

I have the same question (0)

All responses (7)

Answers (0)

Mira Ghaly 11,413 Moderator on at

Like (0)

Report

@JRavas

So you are trying to filter which view another view where AAD is a lookup or filtering the AAD user lookup itself?

Was this reply helpful? Yes No
JR-15081603-0 18 on at

Like (0)

Report

@Mira_Ghaly I have the lookup column that references the virtual table in the form for my main table. For that main table, I am trying to create a personalize view that only shows items that the viewer owns. In SharePoint I would set up a view filter formula that filters on <user> = [Me]. I would like to be able to do the same thing here.

Is this even possible?

Was this reply helpful? Yes No
Mira Ghaly 11,413 Moderator on at

Like (0)

Report

@JRavas

Looks like this is a limitation the operator equals current user is not there when you select the AAD User Table.

Was this reply helpful? Yes No
Mira Ghaly 11,413 Moderator on at

Like (0)

Report

@JRavas

If you are using this lookup in a model driven app for filtration why you don't use the Users table, I am not quite sure about your business scenario if you can provide more details we can think of a workaround.

Was this reply helpful? Yes No
Ami K 15,679 Super User 2024 Season 1 on at

Like (0)

Report

@JRavas - use the User table instead of the AAD table to do this.

Note - ensure that the Searchable checkbox is checked in your lookup column in order for the field to appear as an option in the filters

Was this reply helpful? Yes No
JR-15081603-0 18 on at

Like (0)

Report

@Mira_Ghaly & @Amik - thank you for the replies. My use case is that I am building an extension to the Power Platform Center of Excellence, where I am providing a means to register SharePoint Lists and Power BI reports that are being created by our Citizen Developers. I want to no only register the makers, but the owners and an additional contact. The CoE maintains it's own Maker table. Was looking for a way to support the other 2 users without having to maintain a table - if possible and yet filter on "me" so I can see what is mine.

The documentation seems to indicate that it contains users who use Dataverse. In these cases, the user many not use Dataverse specifically. Apologies as I am new at using Dataverse and model drive apps. Not sure if I can just add people to the User table or if the best practice approach is to create my own "user" tables.

Was this reply helpful? Yes No
SallyO 9 on at

Like (0)

Report

Apparently the AAD filter is a reported BUG with Microsoft (2022!).
the reason we would not want to use the users table if it isnt populated with users until they enter the app for the first time. so if was to import sharepoint data any user fields will crash.

Was this reply helpful? Yes No