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 / Building a data struct...
Power Apps
Unanswered

Building a data structure/relationships

(0) ShareShare
ReportReport
Posted on by 216

I usually work with SharePoint as my datasource but for this piece of work, I am experimenting with Dataverse primarily because of the ability to create relationships with the data. However, I am finding it a little tricky to think how best to structure the tables/relationships.

 

Essentially my users need to start by selecting a project. For each project, there is a type of shopping list of items which will always be the same. However, for each item, there are further characteristics that need to be defined. The user needs to input this information. That list is then sent to another team who create another revision. Further revisions are made until the list is finalised.

 

I want all the project data to be in the same environment. I am going to use a canvas app for the selection and input. So far I have a Projects table and a table with the 'Shopping list' and characteristics. But essentially that shopping list will need to be duplicated when a project is created. Any advice on how best to do this is appreciated.

 

I have the same question (0)
  • christophraidl Profile Picture
    38 on at

    Hi,

    so let me try to rephrase that to see if i understood you correctly.

    You have multiple projects and each of those projects has a shopping list.
    Each shopping list contains out of multiple items (which are always the same).

    Based on this I would have multiple suggestions, but let me start with the first one.
    Normally the relationship would be like this.

    Project (N:1) Shopping List (1:N) Items
    Which means multiple projects can have the same shopping list connected to it and a shopping list has multiple items connected to it.

    Why is it essential to duplicate the shoppinglist then when the items are always the same?

    Hope that helps, but if you have more input here let me know!

  • AhmedSalih Profile Picture
    6,680 Moderator on at

    Hello, @CAlvy, based on your requirements I can see that you will need 4 tables: Projects, Items, Preject_Items, and Revisions. To avoid the duplications, you can design your ERD as follows:

    mermaid-diagram-2024-03-03-185249.png

    NOTE: in Dataverse, you will need to use the Lookup columns for the FKs and Alternate Keys for the PKs.

     


     

    If my reply helped you, please give a 👍 If it solved your issue, please give a 👍 & accept it as the Solution to help other community members find it more.

    Visit my Blog: ahmedsalih.blog

    Visit my YouTube Channel: https://www.youtube.com/@powerplatformplace/videos

  • Shashank Bhide Profile Picture
    946 Moderator on at

    Sounds like you need to create a standard 1:N relationship between your "project" table and "shopping list item" table, that way, each project can have its own sub-list of shopping items.

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

Introducing the 2026 Season 1 community Super Users

Congratulations to our 2026 Super Users!

Kudos to our 2025 Community Spotlight Honorees

Congratulations to our 2025 community superstars!

Leaderboard > Power Apps

#1
WarrenBelz Profile Picture

WarrenBelz 529 Most Valuable Professional

#2
Haque Profile Picture

Haque 230

#3
Kalathiya Profile Picture

Kalathiya 217 Super User 2026 Season 1

Last 30 days Overall leaderboard