Ultimate Guide to Using Common Data Service relationships and lookup fields in the Power Platform

This video may be the ultimate guide to relationships and lookup fields in Power Platform. Includes creating lookup fields, making other fields searchable in lookup fields, showing related fields in views, changing relationship cascading properties, filtering lookup fields in model-driven apps, making dependent lookup fields, adding additional related entity fields to model-driven forms, adding lookup fields to canvas apps, working with polymorphic fields to canvas apps, reading lookup fields in Power Automate, editing lookup fields in Power Automate, and clearing lookup fields in Power Automate.

[deeplearning]

Hello, thank you for sharing. This is great!
I'm very new to power apps and trying to create a model driven app, where user can View some Contract information for their respective projects.

On the application, user should be able to select 1) Industry name (a set of options) 2) Client name 3) Project ID and 4) Contract Category Name (Payment, Interest, Termination etc).

After "Contract Category" selection, user should see the details of the specific category [e.g. for Payment - Term, Contract Clause] for the corresponding Project ID.

I'm facing challenges here, especially in establishing the relationships between Project ID, Contract Category Name and Category details. Would you please suggest what would be the best way to address this?

[truegamers]

Hello Thanks for the vedio,
I am building a powerapps portal and am using common data services entity, So what I want is to view this records in the portal according to the login user vs a field called Email1 in my entity and it is text type not lookup because when i created my entity I get it's data from sql.