Common Data Service (CDS) Relationships in PowerApps (Canvas)

[@AudrieGordon]

Absolutely awesome video! You break down the concepts beautifully. Can't wait to see others you will upload on Dataverse :)

[@gustavoleo8946]

Wow fancy that intro! Congrats mate for the fantastic explanation!

[@powerappster7641]

Glad you liked it!

[@GSoftagon]

Establishing a relationship between entities as described by PowerAppster is really cool. I am now able to link my Gallery that has a parent entity and a child entity! Thank you, thank you, and thank you!!!

[@rodmiddleton8268]

Very helpful video. I had no idea how it simplified the referencing of related items. Keep the videos coming! Thanks!

[@GSoftagon]

This is what I have been looking for. Wow! Thank you.

[@simonloughnane6683]

Extremely helpful. Thank you.

[@mariorgutierrezleal]

Great vídeo, very organized, as a newbie, tha is one of the Best i have seen. One question, i'm gueesing that when You save the book, it saves the language name (the actual string), And not the language ID. How do we save the language ID in the book table instead of saving the name string. Thanks

[@KingOfBlades27]

Great video! A noob question: Why should I use always solutions? I understand that if I want to move the logic from one environment to another at some point it is important to use a solution. But if I am building an app for a company in their environment already do I really need to use a solution? Also are entities only usable in one solution or can other apps also see/use those?

[@reloffice9745]

I'd have this same question(s?) - I'm curious about exactly what the difference are when you create you entities from different spots...is this just another MS thing for doing the same thing from different spots or does it open/close different options when created in different locations and what are those differences?

[@Fernando_Calero]

@PowerAppster Hi Keith, thanks for the session. Question, at 30'42'' when I apply the same logic to my app I get this error: "This formula uses scope, which is not presently supported for evaluation:" What you think? #PowerAppster

[@randybristol1484]

I understand how to navigate one relationship using dot notation in PowerAps (Canvas). How do I navigate more than one relationship in PowerApps (Canvas) on a CDS/Dataverse database?

[@Bugugkareng1]

Great, thank you

[@mozgus79ify]

Hi Keith, i hope you're well. Great video. A few things have cleared in my head now. Just one question. Would you rather create a new entity and use 1:N, N:1 relationship or just go with N:N?

[@powerappster7641]

Both, basically its governed by your use case, you have to obey the data model... but, if Power Apps and making the app "Needs" the intersect (bridging) entity then you do it that way.

[@magnusjeppesen]

Great video, that really simplifies the concept! :D But, how would you go around to filter a gallery, to only shows records, that has related (child) records. I.e. only show 'parent records' that has related 'child records' - where the relationship is: parent 1 : m child. Or like in your scenario, only show Authors that has related Books. So if you had an Author that's not related to any Books, that Author would not be shown in the Author gallery.

[@SS-cd1dl]

Sound keeps wigging out