The search in lookup for AAD Users does not work

[365-Assist]

You maybe aware that the Dataverse now supports a logical table for AAD users Announcing the AAD User Virtual Table – Find and add any AAD user to your records. | Microsoft...

However it seems that when searching in a Lookup column in Model Driven App does not work. If anyone know how to make it work let me know.

In example below I type in name (either first or last) and search does not work.

[bipinshan]

Hi,

You would need to open Quick find view and add firstname , lastname column in Add find column.

https://docs.microsoft.com/en-us/dynamics365/customerengagement/on-premises/customize/choose-and-con...

[365-Assist]

Nice thought. However cannot do this as  the AAD Users Table is a virtual table and therefore you cannot add or modify the views.

[JustTinkering]

any news on this, having the same problem

[rampprakash]

Hi @JustTinkering @365-Assist 

Am afraid it is not Possible. Because this table directly associated with AAD Users

[bronsonacoutts]

I have experienced this just like you since the feature was released.  I thought I would give it a little while to see if it was resolved as sometimes things are soon after they are released.  Unfortunately, this hasn't happened.

I have a support ticket open with Microsoft currently and they're looking into the issue.  I'll keep you posted. 🙂

[Fubar]

As per the documentation no search is a limitation for virtual tables (4th bullet down) https://docs.microsoft.com/en-us/power-apps/developer/data-platform/virtual-entities/get-started-ve#...

[bronsonacoutts]

Hi all, 

As I mentioned I raised a ticket with Microsoft Support about this last week sometime.  I have just heard back, and the Product Team has confirmed that it is a BUG and they have provided an ETA that it will be resolved by the end of this week. 🙂

[JustTinkering]

Hi, Thanks for the update, but still a bit sceptic as one of our team had also contact with an engineer and was told it is "as designed", cfr comment from Fubar. 

[ntriplet]

Any update on this?  Having the same issue.  Really preventing us to be able to transition to Dataverse and Model-Driven apps as it is needed in so many use cases.