Power Apps One-to-Many Relationship CRM for Customers / Cars

[@PowerAppsTutorial]

🍬 Get my free video course, access to my free community, and, if you would like, you can book a call with me here: go.superpowerlabs.co/opt-in-page-page ⬅

[@basehumax]

Wow Thank you Darren am now addicted to your channel and love it.

[@PowerAppsTutorial]

Thanks so much for the love! 😊

[@mewweb8908]

Nice useful things what IAM looking for... Keep rocking,,,,,

[@PowerAppsTutorial]

Thank you so much 😀👍👍

[@antoniokimble5286]

Greetings! I happened upon your video series when I used "PowerApps Inventory Management" to look into creating one. I had a general idea but I want to point out a few things that I really appreciated. 1. at the beginning and end where you show your list of items of detail. I think this is called a data model, right? I've never actually seen it in practice so I never used it up to this point in the apps I've created at my company. After this though, I see it's extremely important. 2. using the ID as a relationship without using lookup columns. I find those really limiting in case you need to change that column or morph it into something else based on business needs so I don't use them. Instead, I will make collections from the columns in the sources I need and use those in my combo boxes that I replace for the regular dropdowns in the form. 3. Speaking of forms, the fact you went formless is awesome! Months ago, I created a CapEx app without a form but I didn't at the time know how to reference anything back so pretty much it was fire and forget. This was the missing link. 4. using the ID to reference and associate the items to one person was also a missing link for me. This way, I can use multiple many-to-one relationships if need be. If I were to build some automation for this, I have an idea of how'd I'd go about bringing in the information for each user, but I would like to ask to see if I'm in the right ballpark. Would this consist of using either a join or union to accomplish this? I'm thinking this may not even be needed using the ODATA filter query of UserID eq 'ID' or something to that effect. I watch guys like Reza Dorrani, Shane Young, and David Christian so I'm gonna give you a shout out in their videos so more people can check you out.

[@PowerAppsTutorial]

Wow! Thanks for all of that. I think that is the most detailed comment I've ever received. Thanks!! 😄👍 #1 - Yes, you could call it a model, but it is some rough documentation I had created with the client I'm building the app for. #2 - I see. #3 - Very cool. #4 - Yes, this is the way I handle relationships with SharePoint lists. Thanks again!

[@basehumax]

Darren, quick question, a while since I have build an canvas app without responsive as all my apps are responsive but it will involve lot of work if I have to add different sections like One-to-Many Relationship Customer/Vehicle App in one screen so I have decided to build normal app like your canvas app ❤️, but, am having hard time the sizes to set, so will you tell me please, the sizes set on your canvas app like Orientation, Size, Scale to fit , lock aspect ratio, lock Orientation. sorry for asking lot of question and thank you.

[@PowerAppsTutorial]

No problem. Thanks for asking! I keep the defaults as is unless I have a good reason to change them. For this particular app, Orientation is Landscape, Size is the default 16:9. Scale to fit, Lock aspect ratio, and Lock orientation are all set to On. These type of settings should work fine for most, if not all of users who are using the app in a desktop browser or a tablet. If users will be using on their phones, it should still work fine if they turn their phones to be sideways, but you can always create a phone version if the need was there. Usually, the users who really need a phone layout only need one or two screens or a subset of the features anyways. I hope that helps! 😀