We have 2 SharePoint lists:-
1) Assets
2) Spare Parts
Now a Spare Part can be linked to more than one Asset and an Asset can have more than one Spare Part. Now the straight forward way to implement this inside SharePoint is to create a lookup field which allow multiple selection either inside the Assets list or inside the Spare Parts list. but this approach has the following Disadvantages :-
1) The Lookup column which allow multiple selection can not be indexed inside SharePoint
2) Filter the Assets based on the spare part or Filter the spare parts based on the Asset will not be delegable inside power app.
so what is the correct appraoch to overcome the above 2 limitation?
For example i am thinking instead of creating a lookup field, to create a third list which represents the many to many relation, and store the AssetID and the SparePartId inside it. in this case we can overcome the above 2 limitations.
any advice/comments? on my issue and the appraoch i am proposing?
Thanks
Using a 3rd Sharepoint list as a junction or intersection table seems like a great solution to your problem. This introduces programming complexity but it also provides a scalable solution that will allow you to delegate and to index as you will need. Here is a post discussing similar use case. Here.
The List may have columns like this.. you can also include any meta data you may want access to.
Each record in this list represents a link between an Asset and a Spare Part.
MS.Ragavendar
20
BCBuizer
10
Super User 2025 Season 1
LC-26081402-0
10