The Ultimate Guide to Lookups in Model-Driven Power Apps and Dataverse

This video answers all your questions about how to work with lookups in Dataverse and Model-Driven Power Apps, including
- Why can't I add multiple values to a lookup?
- What if I want to show something other than the primary name in a lookup?
- How can I copy data from a related table?

Jump straight to the section you want using the chapters, or come along for the whole ride and become an expert on all the things you can do with lookups.

Did I miss your question? Let me know in the comments.

Timestamps:
0:00 - Lookups - Your Questions Answered
1:40 - Table relationships in Dataverse
3:45 - Creating lookup columns
8:27 - Primary name and configuring the lookup view
12:29 - Quick View Forms
15:50 - Mapping data from one table to another
22:31 - Filtering - creating dependent lookups
25:56 - Security - stop a user creating a new record in a lookup
26:57 - Importing data - mapping to lookup columns
29:22 - Adding more than one record - choices and many to many tables

[avskadoo]

Yeah it's deficult to grasp everything in 1 go. I can't imagine how much efforts you put to create this content.
Extraordinary work🎉🎉
Thanks a million 😊😊😊

[remuslupinhp]

This is pure gold... this is all that I have been fumbling with for a while now... I Have understood a lot about Model-driven apps from your videos and this fills all the gaps. I am sure I will not be able to implement everything in one go, but this brings in the clarity needed to continuously deepen my learning and familiarity into the world of Model_Driven Apps.

Thanks a lot, Lisa, you da best!

[DaveRound]

The missing link .. Classic Mode Mappings! Marvellous!

[olivergigi]

Your explanations helped a bunch! I am came from the Canvas side, but now I have even more of an appreciation of the Model-Driven. Thank you for your highly informative and clear videos!

[alicedwonderland]

Lisa, the filters in the Quick View are magical! Yesss!!! Thank you for the tip!

[alcantey]

You have bailed me out again Lisa! The quick view widget was the perfect solution in my app. Excellent content. Cheers! 👏👏👏

[franknielsen]

The quick view form was just what i was missing THX. I normally work with Canvas apps, and that is a complete different thing when I need to get related data from a lookup, so this was the missing part of the puzzle. Thanks for showing it - and keep up the good work 👏👏

[alicedwonderland]

Lisa, you're amazing! It makes sense, and I improved the app like crazy because of you. I hope Microsoft is in awe with how much you're helping them getting this product used!

[Leabelias]

Detailed coverage of lookups, one of the confusing topic in model driven app. Thank you very much.

[olmathome]

Very value able and very good described ! Thank you Lisa!

[_loboluis]

Amazing work as usual, Lisa. Thank you so much.

[JontyLP]

Hi Lisa! Videos are really great and informative! Quick question - if you've created a many-many relationship for a model driven app as you did with Books<->Authors (letting PowerApps do this rather than creating an intersect table yourself), how does one import data for Books and Authors (from CSV) and link them if the underlying intersect table is hidden away? Is there some crafty way to do this or an alternative to join the data?

[malchicken]

Great overview. Thank you very much for this 😊🎉.

[mhenrycooper]

Lisa, great video on a topic that is not handled well in the documentation. Microsoft should link to this video when the subject of lookups is searched

[bretttallada]

Yes, please more of this advanced type of content. Javascript onLoad, on Change onSave, PowerFX on command buttons, strategies/frameworks to keep all of this straight in your head 😛

[DavidMercer]

Thank you Lisa your videos are amazing and really well explained and I have used your suggestions effectively in my organisation.

[dougydoe]

Brilliant video with many moving parts. This was what I asked for and I got much more, Thank you. I'll have to watch this again and again to digest it fully. Thanks for taking the time to produce this video. A quick question... is it possible to share the tables you used in a solution? I really want to walk through this and replicate it myself. That's the way I learn quickly. Will really appreciate it.

[marcoerlwein]

muchas gracias Lisa !!! sos una genia, tus videos me han ayudado mucho !!!

[MartinCGaudet]

Hi Lisa. This video helped so much for the demo I have to do in 2 weeks... WOW! Thank you.

[michaellock]

Brilliant!

Thank you for this. It was most helpful. I have one more requirement that you didn't address. It's a of a hybrid of your discussion of making/using lookup tables and the last part of your discussion on M:M relationships.

I have a scenario where I have set of four cascading lookups, where the value of the 2nd lookup is filtered by the selection of the first lookup. The complication I have is that in the definition of the 2nd lookup, it can actually be related to more than one value from the first lookup. Think of the extension of your example of city names in states. The same city name may be unique within the state but it may not be unique within the country or world.

Right now I've implemented this as a set of lookups called Lvl1, Lvl2, Lvl3, and Lvl4 where Lvl2 has a lookup to Lvl1 and so on. In the Lvl 2 table I need to duplicate the value in the name column for each different relationship to a value from Lvl1. I don't like this because it introduces duplication. What I'd prefer is to use M:M relationships between these tables to eliminate the duplication.

Is it possible to use the M:M relationship as the lookup on a form where these four cascading values need to be used? Would I have to manually create the "middle" table and use that as a lookup?

Also, thanks for the section on security and controlling the ability of users to add new lookup values. That was vexing for me and I couldn't find an explanation for how to do that. It did not occur to me that the reason I was seeing the feature was because I am an environment admin.