I'm currently developing a model driven app and am relying on the AAD User table in a many-to-many relationship fashion.
The AAD User, when I browse it manually, appears to have the correct entities. However, when I run the model driven app and open up the field for AAD User, search appears to be broken. I've spent almost a week with different search values etc to try to get anything to work, but it always just displays the same list. Even if I search for a user currently being displayed; same list.
Any ideas on how to resolve this? The fact it's so broken is really slowing me down. Advanced lookup as the same results.
Can you please try searching with Email address and try again.
Please mark as Answer if it is helpful and provide Kudos
Subscribe : https://www.youtube.com/channel/UCnGNN3hdlKBOr6PXotskNLA
I've tried so many different search strings over the last week. That one also didn't work.
No solution. Opened a support case. We verified that the search IS actually working in the background via the advanced find (I also verified this with an API call) so it's the lookup view that doesn't appear to be working. Microsoft is also aware of this table not quite working in the background.
Hi,
I propose a workaround using a PCF control, you find the details on my blog:
https://xrmtricks.com/2022/06/23/model-driven-apps-virtual-tables-how-to-resolve-the-aad-users-looku...
This is a quick workaround while waiting for the Microsoft fix.
Please tick Accept as solution if the answer is useful.
https://xrmtricks.com/
Did you find a way to resolve this or get around the issue?
PCF component posted above is the solution for now.
thanks @RameshMukka. Is there a way to select the default value to the logged in user via a similar method for this lookup field?