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
Super User
Super User

@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
Super User
Super User

@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!

 

@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.  

 

 

@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

Super User of the Month | Drew Poggemann

As part of a new monthly feature in the Community, we are excited to share that Drew Poggemann is our featured Super User for the month of February 2024. If you've been in the Community for a while, we're sure Drew's name is familiar to you, as he is one of our most active contributors--he's been a Super User for five consecutive seasons!   Since authoring his first reply 5 years ago to his 514th solution authored, Drew has helped countless Community members with his insights and expertise. In addition to being a Super User, Drew is also a User Group leader and a Microsoft MVP. His contributions to our Super User sessions and to the new SUIT program are always welcome--as well as his sense of humor and fun-loving way of sharing what he knows with others.   When Drew is not solving problems and authoring solutions, he's busy overseeing the Solution Architecture team at HBS, specializing in application architecture and business solution strategy--something he's been doing for over 30 years. We are grateful for Drew and the amazing way he has used his talent and skills to help so many others in the Community. If you are part of the SUIT program, you got to hear some great tips from Drew at the first SUIT session--and we know he still has much more to share!You can find him in the Community and on LinkedIn. Thank you for all you do, Drew!

Announcing Power Apps Copilot Cookbook Gallery

We are excited to share that the all-new Copilot Cookbook Gallery for Power Apps is now available in the Power Apps Community, full of tips and tricks on how to best use Microsoft Copilot as you develop and create in Power Apps. The new Copilot Cookbook is your go-to resource when you need inspiration--or when you're stuck--and aren't sure how to best partner with Copilot while creating apps.   Whether you're looking for the best prompts or just want to know about responsible AI use, visit Copilot Cookbook for regular updates you can rely on--while also serving up some of your greatest tips and tricks for the Community. Our team will be reviewing posts using the new "Copilot Studio" label to ensure we highlight and amplify the most relevant and recent content, so you're assured of high-quality content every time you visit. If you share a post that gets featured in the curated gallery, you'll get a PM in the Community to let you know!The curated gallery is ready for you to experience now, so visit the new Copilot Cookbook for Power Apps today: Copilot Cookbook - Power Platform Community. We can't wait to see what you "cook" up!      

Celebrating a New Season of Super Users with Charles Lamanna, CVP Microsoft Business Applications

February 8 was the kickoff to the 2024 Season One Super User program for Power Platform Communities, and we are thrilled to welcome back so many returning Super Users--as well as so many brand new Super Users who started their journey last fall. Our Community Super Users are the true heroes, answering questions, providing solutions, filtering spam, and so much more. The impact they make on the Communities each day is significant, and we wanted to do something special to welcome them at our first kickoff meeting of the year.   Charles Lamanna, Microsoft CVP of Business Applications, has stressed frequently how valuable our Community is to the growth and potential of Power Platform, and we are honored to share this message from him to our 2024 Season One Super Users--as well as anyone who might be interested in joining this elite group of Community members.     If you want to know more about Super Users, check out these posts for more information today:    Power Apps: What is A Super User? - Power Platform CommunityPower Automate: What is A Super User? - Power Platform Community Copilot Studio: What is A Super User? - Power Platform Community Power Pages: What is A Super User? - Power Platform Community

February 2024 User Group Update: Welcoming New Groups and Highlighting Upcoming Events

It's a new month and a brand-new year, which means another opportunity to celebrate our amazing User Groups!Each month, we highlight the new User Groups that have joined the community. It's been a busy season for new groups, because we are thrilled to welcome 15 New User Groups! Take a look at the list below, shared by the different community categories. If your group is listed here, give this post a kudo so we can celebrate with you!   We love our User Groups and the difference they make in the lives of our Community! Thank you to all the new User Groups, new User Group leaders--we look forward to hearing about your successes and the impact you will leave!   In addition to our monthly New User Group spotlight, it's a great time to share some of the latest events happening in our User Group community! Take a look at the list below to find one that fits your schedule and need! There's a great combination of in-person and virtual events to choose from. It's a great time of year to connect and engage with User Groups both locally and online. Please Welcome Our NEW User Groups   Power Platform: Heathcare Power Platform User Group Power Platform Connect Hub Power Platform Usergroup Denmark Mexico Norte- Power Platform User Group Pune Power User Group Sudbury Power Platform User GroupMicrosoft User Group GhanaMPPBLR - Microsoft Power Platform Bengaluru User Group Power Apps:   Myrtle Beach Power Platform User GroupAnanseTechWB PowerApps Copilot Studio: Pathfinders Power Platform Community Dynamics365: Cairo, Egypt MSD 365 Business Central/NAV/F&O User GruopMS Dynamics 365 Business Central LatamCincinnati OH D365 F&O User Group February User Group Events February 2024 Cleveland Power Platform User GroupPortallunsj - Februar 2024Indiana D365/AX February User Group MeetingQ1 2024 KC Power Platform and Dynamics 365 CRM Users Group 

Super Users 2024 Season One is Here!

   We are excited to announce the first season of our 2024 Super Users is here! Our kickoff to the new year welcomes many returning Super Users and several new faces, and it's always exciting to see the impact these incredible individuals will have on the Community in 2024! We are so grateful for the daily difference they make in the Community already and know they will keep staying engaged and excited for all that will happen this year.   How to Spot a Super User in the Community:Have you ever written a post or asked for help in the Community and had it answered by a user with the Super User icon next to their name? It means you have found the actual, real-life superheroes of the Power Platform Community! Super Users are our heroes because of the way they consistently make a difference in the Community. Our amazing Super Users help keep the Community a safe place by flagging spam and letting the Community Managers know about issues. They also make the Community a great place to find answers, because they are often the first to offer solutions and get clarity on questions. Finally, Super Users share valuable insights on ways to keep the Community growing, engaging, and looking ahead!We are honored to reveal the new badges for this season of Super Users! Congratulations to all the new and returning Super Users!     To better answer the question "What is a Super User?" please check out this article: Power Apps: What is A Super User? - Power Platform CommunityPower Automate: What is A Super User? - Power Platform Community Copilot Studio: What is A Super User? - Power Platform Community Power Pages: What is A Super User? - Power Platform Community

Did You Attend the Microsoft Power Platform Conference in 2022 or 2023? Claim Your Badge Today!

If you were one of the thousands of people who joined us at the first #MPPC Microsoft Power Platform Conference in 2022 in Orlando--or attended the second-annual conference in Las Vegas in 2023--we are excited to honor you with a special community badge! Show your support for #MPPC Microsoft Power Platform Conference this year by claiming your badge!         Just follow this link to claim your badge for attending #MPPC in 2022 and/or 2023: MPPCBadgeRequest    Want to earn your badge for 2024? Just keep watching our News & Announcements for the latest updates on #MPPC24.

Top Solution Authors
Top Kudoed Authors
Users online (3,013)