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

Win free tickets to the Power Platform Conference | Summer of Solutions

We are excited to announce the Summer of Solutions Challenge!    This challenge is kicking off on Monday, June 17th and will run for (4) weeks.  The challenge is open to all Power Platform (Power Apps, Power Automate, Copilot Studio & Power Pages) community members. We invite you to participate in a quest to provide solutions to as many questions as you can. Answers can be provided in all the communities.    Entry Period: This Challenge will consist of four weekly Entry Periods as follows (each an “Entry Period”)   - 12:00 a.m. PT on June 17, 2024 – 11:59 p.m. PT on June 23, 2024 - 12:00 a.m. PT on June 24, 2024 – 11:59 p.m. PT on June 30, 2024 - 12:00 a.m. PT on July 1, 2024 – 11:59 p.m. PT on July 7, 2024 - 12:00 a.m. PT on July 8, 2024 – 11:59 p.m. PT on July 14, 2024   Entries will be eligible for the Entry Period in which they are received and will not carryover to subsequent weekly entry periods.  You must enter into each weekly Entry Period separately.   How to Enter: We invite you to participate in a quest to provide "Accepted Solutions" to as many questions as you can. Answers can be provided in all the communities. Users must provide a solution which can be an “Accepted Solution” in the Forums in all of the communities and there are no limits to the number of “Accepted Solutions” that a member can provide for entries in this challenge, but each entry must be substantially unique and different.    Winner Selection and Prizes: At the end of each week, we will list the top ten (10) Community users which will consist of: 5 Community Members & 5 Super Users and they will advance to the final drawing. We will post each week in the News & Announcements the top 10 Solution providers.  At the end of the challenge, we will add all of the top 10 weekly names and enter them into a random drawing.  Then we will randomly select ten (10) winners (5 Community Members & 5 Super Users) from among all eligible entrants received across all weekly Entry Periods to receive the prize listed below. If a winner declines, we will draw again at random for the next winner.  A user will only be able to win once overall. If they are drawn multiple times, another user will be drawn at random.  Individuals will be contacted before the announcement with the opportunity to claim or deny the prize.  Once all of the winners have been notified, we will post in the News & Announcements of each community with the list of winners.   Each winner will receive one (1) Pass to the Power Platform Conference in Las Vegas, Sep. 18-20, 2024 ($1800 value). NOTE: Prize is for conference attendance only and any other costs such as airfare, lodging, transportation, and food are the sole responsibility of the winner. Tickets are not transferable to any other party or to next year’s event.   ** PLEASE SEE THE ATTACHED RULES for this CHALLENGE**

Celebrating the June Super User of the Month: Markus Franz

Markus Franz is a phenomenal contributor to the Power Apps Community. Super Users like Markus inspire others through their example, encouragement, and active participation.    The Why: "I do this to help others achieve what they are trying to do. As a total beginner back then without IT background I know how overwhelming things can be, so I decided to jump in and help others. I also do this to keep progressing and learning myself." Thank you, Markus Franz, for your outstanding work! Keep inspiring others and making a difference in the community! 🎉  Keep up the fantastic work! 👏👏   Markus Franz | LinkedIn  Power Apps: mmbr1606  

Copilot Cookbook Challenge | Week 1 Results | Win Tickets to the Power Platform Conference

We are excited to announce the "The Copilot Cookbook Community Challenge is a great way to showcase your creativity and connect with others. Plus, you could win tickets to the Power Platform Community Conference in Las Vegas in September 2024 as an amazing bonus.   Two ways to enter: 1. Copilot Studio Cookbook Gallery: https://aka.ms/CS_Copilot_Cookbook_Challenge 2. Power Apps Copilot Cookbook Gallery: https://aka.ms/PA_Copilot_Cookbook_Challenge   There will be 5 chances to qualify for the final drawing: Early Bird Entries: March 1 - June 2Week 1: June 3 - June 9Week 2: June 10 - June 16Week 3: June 17 - June 23Week 4: June 24 - June 30     At the end of each week, we will draw 5 random names from every user who has posted a qualifying Copilot Studio template, sample or demo in the Copilot Studio Cookbook or a qualifying Power Apps Copilot sample or demo in the Power Apps Copilot Cookbook. Users who are not drawn in a given week will be added to the pool for the next week. Users can qualify more than once, but no more than once per week. Four winners will be drawn at random from the total qualifying entrants. If a winner declines, we will draw again at random for the next winner.  A user will only be able to win once. If they are drawn multiple times, another user will be drawn at random. Prizes:  One Pass to the Power Platform Conference in Las Vegas, Sep. 18-20, 2024 ($1800 value, does not include travel, lodging, or any other expenses) Winners are also eligible to do a 10-minute presentation of their demo or solution in a community solutions showcase at the event. To qualify for the drawing, templates, samples or demos must be related to Copilot Studio or a Copilot feature of Power Apps, Power Automate, or Power Pages, and must demonstrate or solve a complete unique and useful business or technical problem. Power Automate and Power Pagers posts should be added to the Power Apps Cookbook. Final determination of qualifying entries is at the sole discretion of Microsoft. Weekly updates and the Final random winners will be posted in the News & Announcements section in the communities on July 29th, 2024. Did you submit entries early?  Early Bird Entries March 1 - June 2:  If you posted something in the "early bird" time frame complete this form: https://aka.ms/Copilot_Challenge_EarlyBirds if you would like to be entered in the challenge.   Week 1 Results:  Congratulations to the Week 1 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge. Copilot Cookbook Gallery:Power Apps Cookbook Gallery:1.  @Mathieu_Paris 1.   @SpongYe 2.  @Dhanush 2.   @Deenuji 3.  n/a3.   @Nived_Nambiar  4.  n/a4.   @ManishSolanki 5.  n/a5.    n/a

Your Moment to Shine: 2024 PPCC’s Got Power Awards Show

For the third year, we invite you, our talented community members, to participate in the grand 2024 Power Platform Community Conference's Got Power Awards. This event is your opportunity to showcase solutions that make a significant business impact, highlight extensive use of Power Platform products, demonstrate good governance, or tell an inspirational story. Share your success stories, inspire your peers, and show off some hidden talents.  This is your time to shine and bring your creations into the spotlight!  Make your mark, inspire others and leave a lasting impression. Sign up today for a chance to showcase your solution and win the coveted 2024 PPCC’s Got Power Award. This year we have three categories for you to participate in: Technical Solution Demo, Storytelling, and Hidden Talent.      The Technical solution demo category showcases your applications, automated workflows, copilot agentic experiences, web pages, AI capabilities, dashboards, and/or more. We want to see your most impactful Power Platform solutions!  The Storytelling category is where you can share your inspiring story, and the Hidden Talent category is where your talents (such as singing, dancing, jump roping, etc.) can shine! Submission Details:  Fill out the submission form https://aka.ms/PPCCGotPowerSignup by July 12th with details and a 2–5-minute video showcasing your Solution impact. (Please let us know you're coming to PPCC, too!)After review by a panel of Microsoft judges, the top storytellers will be invited to present a virtual demo presentation to the judges during early August. You’ll be notified soon after if you have been selected as a finalist to share your story live at PPCC’s Got Power!  The live show will feature the solution demos and storytelling talents of the top contestants, winner announcements, and the opportunity to network with your community.  It's not just a showcase for technical talent and storytelling showmanship, show it's a golden opportunity to make connections and celebrate our Community together! Let's make this a memorable event! See you there!   Mark your calendars! Date and Time: Thursday, Sept 19th Location: PPCC24 at the MGM Grand, Las Vegas, NV 

Tuesday Tip | Accepting Solutions

It's time for another TUESDAY TIPS, your weekly connection with the most insightful tips and tricks that empower both newcomers and veterans in the Power Platform Community! Every Tuesday, we bring you a curated selection of the finest advice, distilled from the resources and tools in the Community. Whether you’re a seasoned member or just getting started, Tuesday Tips are the perfect compass guiding you across the dynamic landscape of the Power Platform Community.   To enhance our collaborative environment, it's important to acknowledge when your question has been answered satisfactorily. Here's a quick guide on how to accept a solution to your questions: Find the Helpful Reply: Navigate to the reply that has effectively answered your question.Accept as Solution: Look for the "Accept as Solution" button or link, usually located at the bottom of the reply.Confirm Your Selection: Clicking this button may prompt you for confirmation. Go ahead and confirm that this is indeed the solution.Acknowledgment: Once accepted, the reply will be highlighted, and the original post will be marked as "Solved". This helps other community members find the same solution quickly. By marking a reply as an accepted solution, you not only thank the person who helped you but also make it easier for others with similar questions to find answers. Let's continue to support each other by recognizing helpful contributions. 

Reminder: To register for the Community Ambassador Call on June 13th

Calling all Super Users & User Group Leaders     Reminder: To register for the Community Ambassador Call on June 13th—for an exclusive event for User Group Leaders and Super Users! This month is packed with exciting updates and activities within our community.   What's Happening: Community Updates: We'll share the latest developments and what's new in our vibrant community.Special Guest Speaker: Get ready for an insightful talk and live demo of Microsoft Copilot Studio templates by our special guest.Regular Updates: Stay informed with our routine updates for User Groups and Super Users.Community Insights: We'll provide general information about ongoing and upcoming community initiatives. Don't Miss Out: Register Now: Choose the session that fits your schedule best.Check your private messages or Super User Forum for registration links. We're excited to connect with you and continue building a stronger community together.   See you at the call!  

Top Solution Authors
Top Kudoed Authors
Users online (2,310)