Intro to Database Concepts for Power Apps People

[@Sco1ful]

As a newbie, I found this really helpful. Thanks.

[@ShanesCows]

Awesome! That was the goal.

[@prokshitangadi]

I appreciate these videos focusing on the fundamental concepts instead of just the applications. This video, along with the API video, was truly enjoyable.

[@ShanesCows]

Thanks for the comment. That means a lot to me. Glad it helped. 🤩

[@gregmurnock7032]

Normalize until it hurts, de-normalize until it works : ) I sure wish data modeling was still taught/required prior to development!

[@ShanesCows]

Never heard it put that way but I like it! 🤩

[@battle_born]

I learned this concept in one of your videos, the one you reference to here... Since then it feels for me as if I had gained a super power. REALLY! I can't thank you enough for what you do for the community!

[@ShanesCows]

Excellent! Love to hear when people do awesome stuff with the content. 😎

[@GroverParkGeorge]

I really like your plain-language approach to discussing Normalization of data. It's often hard for newbies to wrap their heads around concepts expressed in formal, technical terms. Huzzah.

[@ShanesCows]

Thanks George. That was what I was going for. Relatable instead of fancy. 🥰

[@PowerAppsBuilderGroup]

Good video Shane. I see questions that this video will answer asked all the time on the reddit. Hopefully it finds the right ears!

[@ShanesCows]

Thanks. I am with you, database concepts are confusing for new makers, so hopefully we can help more of them feel less overwhelmed.

[@dougydoe]

This was really really good, Shane. Not a novice I would say but it did deepen my understanding in certain areas so thoroughly enjoyed it. I think you should do more of these "concept understanding" videos and Data Modelling is one area I would like to see more of so happy if you can go into a bit more depth. Generally through, we understanding more of the concepts will be great as that will help us build more robust apps. Thanks for sharing

[@ShanesCows]

Thanks for the kind words. 😎 More core skills to come.

[@oluwatobiyusuf]

Thank you for sharing more light on database Shane

[@ShanesCows]

Happy to help. 🐶

[@MichaelDeBlasis1369]

Just what I was looking for. This is a great video. So many questions answered!

[@codyarnold2939]

I really like your database diagram! What did you use to draw it?

[@ShanesCows]

This made me think 🤔 but the answer is the diagram is a free Canva image. Then I popped the logos on manually. Probably not helpful if you want to build anythign other than exactly what I did. 🤩

[@jeanpierreragequit1726]

Great review. The hardest thing for me happens when if i have to create several tables or 1 table ( grouping all data ). I dont have the knowledge for. The only thing i consider is the 2000 rows sharepoint limit ( no concatenation wide database method ) when i use a lookup function with powerapps.

[@ShanesCows]

Did you check out this video? kzbin.info/www/bejne/bYm7oGytn9N9rMU on making the multiple table approach? It might help.

[@jeanpierreragequit1726]

@@ShanesCows I will. Thx you Shane.

[@hayleeadamson6449]

Such a great video!

[@ShanesCows]

Thanks. 😊 Database concepts are so foundational

[@AtrFS]

In the first example you have both Employee and Manager, but only the employees are normalized, while managers are still stored fully, and not by ID. I've always wondered how this is supposed to be handled, because it's like a second 1 to many relationship between the same tables. Any advice?

[@ShanesCows]

You don't store manager. Manager come from Departments. So by mapping to Executive department you get the manager. Or do you mean the fact that Managers are an employee. Yes, you could create a many-to-one for Managers back to Employees. That wouldn't be uncommon, but that is super confusing so I tried not to go that far in the video. :)

[@GroverParkGeorge]

PMFJI here. You can handle Managers as a Self-Join on the Employee table. You can add a field called "ManagerID" to the Employee table. ManagerID contains the EmployeeID of the Employee (i.e. Manager) to whom that employee reports. A query which includes the Employee table twice, once aliased as "Manager" to distinguish it from the "Employee". Join on the ManagerID to EmployeeID and the resulting query can show each employee with their current manager.

[@CINsyg]

You used to say your apps where not nice looking. This looks like a nice app. But lookup in SP does have some limits when item count increase, where do you set the limit regarding items and lookup.?

[@ShanesCows]

Thanks Carsten. I rarely use SharePoint lookup columns. They have so many little gotchas, if I want a relationship I usually make it myself.

[@antoniobranderas]

Hey Shane, have you noticed that the Enhanced component properties have changed? They wiped out the property type option. All of my Event type custom properties are wiped out. I’m so angry now.

[@ShanesCows]

I had not noticed that :( I will ahve to look around. Sorry

[@antoniobranderas]

@@ShanesCowsAuthoring version 3.24032.26 (NOT yet recommended) corrects the error but doesn’t fix the other error the previous version introduced. On the Power Apps Community > Forums > Get Help with Power Apps > Building Power Apps there is the topic discussion titled: Problem with Event Type property on Components.

[@antoniobranderas]

@@ShanesCowsAnother thread is labeled: Components triggering when editing code

[@antoniobranderas]

@@ShanesCowsThey just pushed authoring version 3.24031.27.

[@MichaelDeBlasis1369]

So In a nutshell; A choice column in a parent table, should become a child table if and when... The choice requires more than 1 column of data to be represented. For example, foods can be a choice so long as you're just tracking foods. Once you begin to track quantity, or price, or size, color, weight. then you need a child table. Period.