cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
Connor55
Resolver I
Resolver I

What type of relationships do i need?

So here's my scenario, I have 2 entities that need to work together.  I have an event production company that has a large inventory of gear - different shows will call for different amounts and types of inventory.  I need to be able to keep track of things coming in and going out.  

 

Shows

- Show name, date, client, etc.

 

Inventory

- Manufacturer, part number, owned stock, in stock, product ID #, barcode #, etc.

 

Is this a many to many relationship?  How would you go about building a list of inventory that would be applied to a show name?  

 

2 ACCEPTED SOLUTIONS

Accepted Solutions

Thanks for the article @v-xida-msft 

https://powerapps.microsoft.com/en-us/blog/one-to-many-relationships-for-canvas-apps/

Looking at this - I think my issue is I need another entity.  It seems like the best way to do this is to have:

Show Details

- Show ID

- Show Name

- Show Date

- etc.

 

Inventory

- Manufacturer

- Part #

- Product ID

- Barcode

- In Stock Quantity

- Owned Stock Quantity

- etc.

 

Show Inventory

- Show ID

- Product ID

- Quantity

- Rental Price

- etc.

 

Relationships:

Inventory has a 1:n relationship with Show Inventory via the "Product ID"

Show Inventory has a n:1 relationship with Show Details via "Show ID"

 

I think this is the right solution - I'll update this thread if I run into an issue with non-serial vs serialized items.  

 

 

View solution in original post

@poweractivate 
From my research, you're right.  The non-serial vs serial items does pose an issue.  The solution is a many to many relationship - since one item can be related to multiple Show Details entity.  

 

Now there's the issue of keeping track of stock.  I'll tag you in a new thread I'm adding for this.  

 

Thanks for all your help so far!

View solution in original post

8 REPLIES 8
poweractivate
Most Valuable Professional
Most Valuable Professional

@Connor55 

One Inventory has Many Show to our understanding.

 

A one to many relationship, with Inventory on the one side, and Show on the many side

 

However, if Many to many came to mind first, maybe your scenario may be more complex, maybe you need more Entities that have 1:N or N:1 in between the model in your case, so you may need to think about that.

poweractivate
Most Valuable Professional
Most Valuable Professional

@Connor55 

Some more elaboration:

 

If One Inventory has Many Show, then the following is usually the result:

 

  1. Inventory would be able to list the associated Show
  2. The Lookup field is on the Many side actually. So the Show has only one Inventory. However, the Inventory can have many Show
    1. In other words, on your Show form, there is one Lookup field for Inventory
    2. However, two or more Show records could be referencing the same Inventory - hence, One Inventory, Many Show
    3. Thus, each Inventory record can have an associated view that "shows" you all the "Show" for which the Lookup field was set to that same Inventory

Does the above fit your case?

If you invert the One to many, then it is as follows:

 

If One Show has Many Inventory, then the following is usually the result:

 

  1. It is the Show record, which would be able to list the associated Inventory
  2. The Lookup field is on the Many side actually. So the Inventory would be the one that has only one Show in this case
    1. In other words, on your Inventory form, there is one Lookup field for Show
    2. However, two or more Inventory records could be referencing the same Show - hence, One Show, Many Inventory
    3. Thus, each Show record can have an associated view that "shows" you all the "Inventory" for which the Lookup field was set to that same Show

 

Does neither of the above work? Then you may need to recheck your model and think it through more.

If one of the above does work, then choose the one that best fits your scenario.

v-xida-msft
Community Support
Community Support

Hi @Connor55 ,

Could you please share a bit more about your scenario?

Is a show name related to multiple inventory records on your side?

 

If a show name is related to multiple inventory records, but a inventory record could only be bind to single one show name, I think the "One-to-Many" relationship would be better in your scenario.

 

On your side, you could consider create a "One-to-Many" relationship from your Shows Entity to your Inventory Entity. Then there is a LookUp field generated automatically within your Inventory Entity. After that, you could consider filter your Inventory records based on the generated LookUp field.

 

Add a Gallery (ShowsGallery) in your app, set the Items property to following:

Shows

add another Gallery control (InventoryGallery) in your app, then set the Items property to following

Filter(Inventory, LookUpField.IdentifierColumn = ShowsGallery.Selected.IdentifierColumn)

Note: The LookUpField represents the generated LookUp field in your Inventory Entity based on the "One-to-Many" relationship.

 

Please check and see if the following blog would help in your scenario:

https://powerapps.microsoft.com/en-us/blog/one-to-many-relationships-for-canvas-apps/

 

Best regards,

Community Support Team _ Kris Dai
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

@v-xida-msft 
@poweractivate 

 

A barcode in this case is a unique number assigned to an item.

A product ID is a number that refers to a specific model of an item.

 

There are two types of Product ID's:

Serialized - multiple barcodes refer to the same Product ID 

Non-serialized - a single barcode refers to a single Product ID (instead of multiple barcodes, a fixed quantity is attached)

 

The one "Show" to many "Inventory" works for serialized items, but the non-serial items will share different shows at different quantities.

 

My solution was to create a new entity for each show - having a one "Show Entity" to many "Inventory" relationship - a column named InStock would update whenever an item is added to a show.

 

HOWEVER, I don't know of a way to automate adding an entity.

 

Looking forward to your thoughts, thank you!

 

poweractivate
Most Valuable Professional
Most Valuable Professional

@Connor55 

 

You could attempt something like this:

 

  1. One "Show" to many "Inventory" 
  2. For Inventory, you have One "Inventory" to many "Barcode" - so multiple barcodes could be referencing same Inventory (the Lookup would be on the inventory)
  3.  For your one-to-one, you could have a Field under "inventory" for a single barcode.
  4.  You can have a "Two Options" Option set with two options: "Single Barcode" or "Multiple Barcode"
  5. On the Inventory Form, you could use a Business Rule to decide the following:
    1.  If the Two Options field is set to Single Barcode ->
      1. show the single barcode field,
      2. clear any value for multiple barcode - then
      3. hide multiple barcode field
      4. set Single Barcode as required - then
      5. set Multiple Barcode as Optional
    2.  If the Two Options field is set to Multiple Barcode -> 
      1. show the multiple barcode field,
      2. clear any value for single barcode - then
      3. hide single barcode field
      4. set Multiple Barcode as required - then
      5. set Single Barcode as Optional

See if this works above for you.

Thanks for the article @v-xida-msft 

https://powerapps.microsoft.com/en-us/blog/one-to-many-relationships-for-canvas-apps/

Looking at this - I think my issue is I need another entity.  It seems like the best way to do this is to have:

Show Details

- Show ID

- Show Name

- Show Date

- etc.

 

Inventory

- Manufacturer

- Part #

- Product ID

- Barcode

- In Stock Quantity

- Owned Stock Quantity

- etc.

 

Show Inventory

- Show ID

- Product ID

- Quantity

- Rental Price

- etc.

 

Relationships:

Inventory has a 1:n relationship with Show Inventory via the "Product ID"

Show Inventory has a n:1 relationship with Show Details via "Show ID"

 

I think this is the right solution - I'll update this thread if I run into an issue with non-serial vs serialized items.  

 

 

poweractivate
Most Valuable Professional
Most Valuable Professional

@Connor55 

 


@Connor55 wrote:

Relationships:

Inventory has a 1:n relationship with Show Inventory via the "Product ID"

Show Inventory has a n:1 relationship with Show Details via "Show ID"

 

I think this is the right solution - I'll update this thread if I run into an issue with non-serial vs serialized items.  

 

 


 

Connor, you are likely right for your case. 

 

You have the "N" in the middle Show Inventory

 

1(Inventory):N(ShowInventory):1(ShowDetails)

 

That means in your case,

1.  In your Product ID, each ShowInventory can be tied to one Inventory, so the lookup field (Product ID) is on the ShowInventory record form for associated Inventory record.

 

Consequently, an Inventory record can have a new associated ShowInventory record created from that Inventory form (equivalent to creating a new ShowInventory and populating the lookup field (Product ID) with the Inventory it was created from).

 

Then, any one Inventory record can have one or more ShowInventory

 

 

2. In your Show ID , each ShowInventory can be tied to one ShowDetails, so there is another lookup field ( Show ID ) on the ShowInventory record form for associated ShowDetails record.

 

Consequently, a ShowDetails, record can have a new associated ShowInventory record created from that Inventory form (equivalent to creating a new ShowInventory and populating the lookup field (  Show ID ) with the ShowDetails record it was created from).

 

Then, any one ShowDetails, record can have one or more ShowInventory

 

 

However, regarding your barcode, we wonder if now our previous suggestion becomes relevant at this point (in addition to what you have implemented so far) for the Serialized versus Non Serialized inventory.

 

 


@dynamicsedge wrote:
  • For Inventory, you have One "Inventory" to many "Barcode" - so multiple barcodes could be referencing same Inventory (the Lookup would be on the inventory)
  •  For your one-to-one, you could have a Field under "inventory" for a single barcode.
  •  You can have a "Two Options" Option set with two options: "Single Barcode" or "Multiple Barcode"
  • On the Inventory Form, you could use a Business Rule to decide the following:
    1.  If the Two Options field is set to Single Barcode ->
      1. show the single barcode field,
      2. clear any value for multiple barcode - then
      3. hide multiple barcode field
      4. set Single Barcode as required - then
      5. set Multiple Barcode as Optional
    2.  If the Two Options field is set to Multiple Barcode -> 
      1. show the multiple barcode field,
      2. clear any value for single barcode - then
      3. hide single barcode field
      4. set Multiple Barcode as required - then
      5. set Single Barcode as Optional

 

 

 


Alternatively @Connor55  if you would prefer that 1:1 is not modeled as an attribute as in our original suggestion, and if you prefer that it must be a lookup, you could also instead have a setting in the Barcode of Two Options - Serialized or Non-Serialized

Then you could write a CDS plugin that checks on creation of a new Barcode:

 

1. If the Barcode is Non-Serialized and associated Inventory is already associated with one Barcode that is being attempted to be updated, the change is rejected.

2. If the Barcode is already Serialized and is already associated with more than one Barcode, and the attempt is to change it to Non Serialized, the change is rejected.

3. If the Barcode is Non-Serialized and somehow it became associated with more than one Barcode, the model was breached and a critical error message should be displayed, and if this ever happens, then it was not implemented correctly.

4. It is possible to apply Business Rules directly on the Entity (not just the form) using the Entity scope under Business Rules - but we are not sure the above can be done as Business Rules (probably cannot) - whereas the original suggestion we had can be done without any complex plugins and using just Business Rules.

 

We think the plugin approach is more complex than the approach we said first. Therefore the approach we said the first time of modeling 1:1 as an attribute and doing it with Business Rules might be preferable.

@poweractivate 
From my research, you're right.  The non-serial vs serial items does pose an issue.  The solution is a many to many relationship - since one item can be related to multiple Show Details entity.  

 

Now there's the issue of keeping track of stock.  I'll tag you in a new thread I'm adding for this.  

 

Thanks for all your help so far!

Helpful resources

Announcements

Exclusive LIVE Community Event: Power Apps Copilot Coffee Chat with Copilot Studio Product Team

  It's time for the SECOND Power Apps Copilot Coffee Chat featuring the Copilot Studio product team, which will be held LIVE on April 3, 2024 at 9:30 AM Pacific Daylight Time (PDT).     This is an incredible opportunity to connect with members of the Copilot Studio product team and ask them anything about Copilot Studio. We'll share our special guests with you shortly--but we want to encourage to mark your calendars now because you will not want to miss the conversation.   This live event will give you the unique opportunity to learn more about Copilot Studio plans, where we’ll focus, and get insight into upcoming features. We’re looking forward to hearing from the community, so bring your questions!   TO GET ACCESS TO THIS EXCLUSIVE AMA: Kudo this post to reserve your spot! Reserve your spot now by kudoing this post.  Reservations will be prioritized on when your kudo for the post comes through, so don't wait! Click that "kudo button" today.   Invitations will be sent on April 2nd.Users posting Kudos after April 2nd. at 9AM PDT may not receive an invitation but will be able to view the session online after conclusion of the event. Give your "kudo" today and mark your calendars for April 3rd, 2024 at 9:30 AM PDT and join us for an engaging and informative session!

Tuesday Tip: Unlocking Community Achievements and Earning Badges

TUESDAY TIPS are our way of communicating helpful things we've learned or shared that have helped members of the Community. Whether you're just getting started or you're a seasoned pro, Tuesday Tips will help you know where to go, what to look for, and navigate your way through the ever-growing--and ever-changing--world of the Power Platform Community! We cover basics about the Community, provide a few "insider tips" to make your experience even better, and share best practices gleaned from our most active community members and Super Users.   With so many new Community members joining us each week, we'll also review a few of our "best practices" so you know just "how" the Community works, so make sure to watch the News & Announcements each week for the latest and greatest Tuesday Tips!     THIS WEEK'S TIP: Unlocking Achievements and Earning BadgesAcross the Communities, you'll see badges on users profile that recognize and reward their engagement and contributions. These badges each signify a different achievement--and all of those achievements are available to any Community member! If you're a seasoned pro or just getting started, you too can earn badges for the great work you do. Check out some details on Community badges below--and find out more in the detailed link at the end of the article!       A Diverse Range of Badges to Collect The badges you can earn in the Community cover a wide array of activities, including: Kudos Received: Acknowledges the number of times a user’s post has been appreciated with a “Kudo.”Kudos Given: Highlights the user’s generosity in recognizing others’ contributions.Topics Created: Tracks the number of discussions initiated by a user.Solutions Provided: Celebrates the instances where a user’s response is marked as the correct solution.Reply: Counts the number of times a user has engaged with community discussions.Blog Contributor: Honors those who contribute valuable content and are invited to write for the community blog.       A Community Evolving Together Badges are not only a great way to recognize outstanding contributions of our amazing Community members--they are also a way to continue fostering a collaborative and supportive environment. As you continue to share your knowledge and assist each other these badges serve as a visual representation of your valuable contributions.   Find out more about badges in these Community Support pages in each Community: All About Community Badges - Power Apps CommunityAll About Community Badges - Power Automate CommunityAll About Community Badges - Copilot Studio CommunityAll About Community Badges - Power Pages Community

Tuesday Tips: Powering Up Your Community Profile

TUESDAY TIPS are our way of communicating helpful things we've learned or shared that have helped members of the Community. Whether you're just getting started or you're a seasoned pro, Tuesday Tips will help you know where to go, what to look for, and navigate your way through the ever-growing--and ever-changing--world of the Power Platform Community! We cover basics about the Community, provide a few "insider tips" to make your experience even better, and share best practices gleaned from our most active community members and Super Users.   With so many new Community members joining us each week, we'll also review a few of our "best practices" so you know just "how" the Community works, so make sure to watch the News & Announcements each week for the latest and greatest Tuesday Tips!   This Week's Tip: Power Up Your Profile!  🚀 It's where every Community member gets their start, and it's essential that you keep it updated! Your Community User Profile is how you're able to get messages, post solutions, ask questions--and as you rank up, it's where your badges will appear and how you'll be known when you start blogging in the Community Blog. Your Community User Profile is how the Community knows you--so it's essential that it works the way you need it to! From changing your username to updating contact information, this Knowledge Base Article is your best resource for powering up your profile.     Password Puzzles? No Problem! Find out how to sync your Azure AD password with your community account, ensuring a seamless sign-in. No separate passwords to remember! Job Jumps & Email Swaps Changed jobs? Got a new email? Fear not! You'll find out how to link your shiny new email to your existing community account, keeping your contributions and connections intact. Username Uncertainties Unraveled Picking the perfect username is crucial--and sometimes the original choice you signed up with doesn't fit as well as you may have thought. There's a quick way to request an update here--but remember, your username is your community identity, so choose wisely. "Need Admin Approval" Warning Window? If you see this error message while using the community, don't worry. A simple process will help you get where you need to go. If you still need assistance, find out how to contact your Community Support team. Whatever you're looking for, when it comes to your profile, the Community Account Support Knowledge Base article is your treasure trove of tips as you navigate the nuances of your Community Profile. It’s the ultimate resource for keeping your digital identity in tip-top shape while engaging with the Power Platform Community. So, dive in and power up your profile today!  💪🚀   Community Account Support | Power Apps Community Account Support | Power AutomateCommunity Account Support | Copilot Studio  Community Account Support | Power Pages

Super User of the Month | Chris Piasecki

In our 2nd installment of this new ongoing feature in the Community, we're thrilled to announce that Chris Piasecki is our Super User of the Month for March 2024. If you've been in the Community for a while, we're sure you've seen a comment or marked one of Chris' helpful tips as a solution--he's been a Super User for SEVEN consecutive seasons!       Since authoring his first reply in April 2020 to his most recent achievement organizing the Canadian Power Platform Summit this month, Chris has helped countless Community members with his insights and expertise. In addition to being a Super User, Chris is also a User Group leader, Microsoft MVP, and a featured speaker at the Microsoft Power Platform Conference. His contributions to the new SUIT program, along with his joyous personality and willingness to jump in and help so many members has made Chris a fixture in the Power Platform Community.   When Chris isn't authoring solutions or organizing events, he's actively leading Piasecki Consulting, specializing in solution architecture, integration, DevOps, and more--helping clients discover how to strategize and implement Microsoft's technology platforms. We are grateful for Chris' insightful help in the Community and look forward to even more amazing milestones as he continues to assist so many with his great tips, solutions--always with a smile and a great sense of humor.You can find Chris in the Community and on LinkedIn. Thanks for being such a SUPER user, Chris! 💪🌠

Find Out What Makes Super Users So Super

We know many of you visit the Power Platform Communities to ask questions and receive answers. But do you know that many of our best answers and solutions come from Community members who are super active, helping anyone who needs a little help getting unstuck with Business Applications products? We call these dedicated Community members Super Users because they are the real heroes in the Community, willing to jump in whenever they can to help! Maybe you've encountered them yourself and they've solved some of your biggest questions. Have you ever wondered, "Why?"We interviewed several of our Super Users to understand what drives them to help in the Community--and discover the difference it has made in their lives as well! Take a look in our gallery today: What Motivates a Super User? - Power Platform Community (microsoft.com)

March User Group Update: New Groups and Upcoming Events!

  Welcome to this month’s celebration of our Community User Groups and exciting User Group events. We’re thrilled to introduce some brand-new user groups that have recently joined our vibrant community. Plus, we’ve got a lineup of engaging events you won’t want to miss. Let’s jump right in: New User Groups   Sacramento Power Platform GroupANZ Power Platform COE User GroupPower Platform MongoliaPower Platform User Group OmanPower Platform User Group Delta StateMid Michigan Power Platform Upcoming Events  DUG4MFG - Quarterly Meetup - Microsoft Demand PlanningDate: 19 Mar 2024 | 10:30 AM to 12:30 PM Central America Standard TimeDescription: Dive into the world of manufacturing with a focus on Demand Planning. Learn from industry experts and share your insights. Dynamics User Group HoustonDate: 07 Mar 2024 | 11:00 AM to 01:00 PM Central America Standard TimeDescription: Houston, get ready for an immersive session on Dynamics 365 and the Power Platform. Connect with fellow professionals and expand your knowledge. Reading Dynamics 365 & Power Platform User Group (Q1)Date: 05 Mar 2024 | 06:00 PM to 09:00 PM GMT Standard TimeDescription: Join our virtual meetup for insightful discussions, demos, and community updates. Let’s kick off Q1 with a bang! Leaders, Create Your Events!    Leaders of existing User Groups, don’t forget to create your events within the Community platform. By doing so, you’ll enable us to share them in future posts and newsletters. Let’s spread the word and make these gatherings even more impactful! Stay tuned for more updates, inspiring stories, and collaborative opportunities from and for our Community User Groups.   P.S. Have an event or success story to share? Reach out to us – we’d love to feature you!

Top Solution Authors
Top Kudoed Authors
Users online (6,299)