How to Set Up Relationships in Power Apps 

Thanks for that. Join my free community for more: www.skool.com/power-apps-community🍬

Glad you enjoyed it! Use this to up your game: learn.powerappstutorial.com/Masterclass?r_done=1

Awesome! Thank you!

Great to hear! Makes my day! 😀👍

Am glad it helps. Theres alot going on in our free community, be sure to join: www.skool.com/power-apps-community

You're very welcome!

Thanks so much!

You're welcome!

Patch is great! I'm glad to hear it was helpful! I explain and used it more on today's live stream: ru-vid.com/video/%D0%B2%D0%B8%D0%B4%D0%B5%D0%BE-5pHkinahfsc.html

Glad it was helpful! Join my free PowerApps Community here to lower your learning curve 🚀😎. www.skool.com/power-apps-community

Glad I could help!

Glad it was helpful! Thanks!

I don't see why you couldn't. When you say "view", do you mean gallery?

Good question. Lookups and other complex column types are problematic in Power Apps and can cause delegation issues. SharePoint natively was not designed to work with Power Apps. Stick with simple column types (text, numbers, datetime, etc).

So glad you enjoyed it!

Glad I could help!😊

Thanks for watching.

No, it doesn't have to be unique, unless you go into the field settings and click yes to "Enforce unique values". That's what ID is generally used for. 😊

You can't patch two data sources with the one patch. Just have one patch, get the ID, then patch the many relationship with that ID right after. Separate the patch statements with a semicolon. 👍

Glad it was helpful!😊

You could update the data into an Excel file by bringing it into Power Apps through OneDrive. Here's a video where I work with an Excel table: ru-vid.com/video/%D0%B2%D0%B8%D0%B4%D0%B5%D0%BE-5O5XQrHQMec.html

You're welcome!

SharePoint lists always create a column called "ID" and it acts like an auto incrementing number. Does that answer your question?

@@PowerAppsTutorial Yes it did, thank you very much.

Welcome! 😊

Just a number. If you use SharePoint lookup type columns, you may run into delegation issues when trying to query on that field.

What do you mean by "SharePoint web level edit"? Are you talking about if a user goes directly to the SharePoint list? I generally don't allow that. You could create a lookup column if you wanted, but that could create delegation issues in Power Apps.

Thanks! 😁

Thank you very much!😎

lol... I am just a teacher who is still learning himself! 😋

You're welcome!😀

Thank you for watching :D

Thanks for watching☺️

Check out this video: ru-vid.com/video/%D0%B2%D0%B8%D0%B4%D0%B5%D0%BE-cml6hcMb7V0.html&lc=UgxCaFdiNOeNuDFvNr14AaABAg

Good question! What I do, is that I make all the users of my app "members" of the SharePoint site. It's always worked well for me!

Sure, but there is some configuration needed inside the forms to pull it off. 😊👍

@@PowerAppsTutorial please explain how can to do it ?

Post your questions to our free community here for quick help: www.skool.com/power-apps-community

Appreciate it

In PowerApps, setting up relationships among three tables (Brand, Sectors, and Subsectors) with a many-to-many structure involves using a junction table to handle the relationships. First, create a junction table that includes Brand_id, Sectors_id, and Subsectors_id as its primary fields, each serving as a foreign key to the respective tables. In PowerApps, when you add these tables as data sources, you can utilize the Lookup function to establish connections. For example, in a gallery or form, you can show related data by filtering the junction table based on a selected Brand or Sector. Use the LookUp and Filter functions to display the related Sectors and Subsectors for a selected Brand, creating a nested display where selecting a Brand filters the Sectors, and selecting a Sector further filters the Subsectors.

Thanks for the comment. That is true. If I wanted to use a unique key, sometimes I'll use the Title for that, then create other columns for their name. Dataverse has an auto key column type, which is nice. In both places, you could create a calculated column as well. With SharePoint, I typically recommend sticking with the ID column. 👍👍

@@PowerAppsTutorial sorry to be rude in asking! but would you mind demonstrating that please in dataverse ? i was able to once to do it through VBA in MS Access, and found it helpful in identifying tables junctions and map where the info was coming from etc. As I'm having difficulty in getting my head around the concept of power apps, especially when it comes to SQL code using VB that i'm use not lookup functions

@@adrianconnolly8568 That's a great idea! 😀 Enter any ideas for future videos here: forms.office.com/r/7a2CpDvU0U and I'll try to get to it as soon as I can. Thanks for viewing/interacting. Have you checked out my playlist here where we are currently building out a full ticketing system? ru-vid.com/group/PLMgWds5p226k_Z3JHoyEyOgF6OJbH88GV

Sure! I do have this video here where I do just that. There, I have a many to many relationship between Employees and Privileges with a mapping table in the middle. Let me know what you think! ru-vid.com/video/%D0%B2%D0%B8%D0%B4%D0%B5%D0%BE-zM0qCQQN9MI.html

What about using the lookup columns in SP to reach the same goal ?

​@@johnbrennan8442 You'll run into delegation issues if you're writing a query based on that lookup. That's why I stay away from them.

Too true better to keep it simple SP side therefore making it easy for the users Power Apps end and not having the issue of them breaking things

Thanks for your review💖.. However you can reduce the playback speed or highlight areas where you need help. Be sure to post your questions to our free community: www.skool.com/power-apps-community