web
You’re offline. This is a read only version of the page.
close
Skip to main content

Announcements

News and Announcements icon
Community site session details

Community site session details

Session Id :
Power Platform Community / Forums / Power Apps / Record one to many - b...
Power Apps
Answered

Record one to many - best approach.

(0) ShareShare
ReportReport
Posted on by 18

Hi all,

I am about to start creating an app so I want to ask a question before starting. I will have a situation where one person will be responsible for max 5 countries (all text values). The records will be stored in main SharePoint list. Should I create a separate list for countries or should I store that info within the record of the person in the main list as a multi select dropdown or something else? The idea is later to be able the filter info from the main list in a gallery or if I search by country to find a person.

 

Thank you.

Categories:
  • Verified answer
    Ami K Profile Picture
    15,689 Super User 2024 Season 1 on at

    @powapp77 - typically when creating a one-to-many relationship, in this case between a person (one) and (many) countries, you should create different tables and relate them together using a common identifier. This would be the best option if you need each person to be a single record in your list.

  • Verified answer
    Ami K Profile Picture
    15,689 Super User 2024 Season 1 on at

    @powapp77 sorry for some reason I accidently cleared the rest of my answer after you accepted the solution.

     

    You can certainly create a single list, with each person duplicated per the number of countries they are associated to. You can then associate that list to a Gallery, and then Filter the Gallery on a specific person to display each company associated to that person with e.g.

     

    Filter(
     'Your SharePoint List',
     'Your People Field'.Email = User().Email
    )

     

    Whichever approach depends on the complexities of your app, but I find that as data volumes increase, relating multiple tables is more sustainable.

     

    It is also important to note that you should avoid using complex data types such as Choices and LookUp columns in your List/s, and handle the relationships entirely in the app interface using delegable Filter and LookUp functions.

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Season of Sharing Community Challenge Winners!

Congratulations to our community stars!

Kudos to our 2025 Community Spotlight Honorees

Expanding mentorship, skilling, and AI innovation

Leaderboard > Power Apps

#1
11manish Profile Picture

11manish 337 Super User 2026 Season 2

#2
M Bilal Khan Profile Picture

M Bilal Khan 250

#3
Mohsin Ali Profile Picture

Mohsin Ali 225

Last 30 days Overall leaderboard