I have built a model driven app to manage projects and the associated financials. Within the solution there are 3 related tables (Projects, Financials, Microsoft Entra ID). On the Project form, I have a look up field to assign a project to a user from the Microsoft Entra ID table. That connection and lookup is working as intended. I am now wanting to create a view on the financial table that includes the assigned user. When I add the User field from the related project table, I receive a SQL error message (see attached image). Is this a known issue? Is there something I need to be doing differently or is this a limitation for model-driven app?
Unsure about this specific error but I've always found using that table to be a little problematic. Try making your lookup columns to Users (systemuser) instead of the Entra ID table.
Was this reply helpful?YesNo
Under review
Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.