Hi
In the Level 1 Model for Unicorn, Size was defined as a List and the Products file imported shows a 1-to-1 relationship for Product -> Size.
Product Code | Product Name | Family Code | Size |
P001 | Nutzo Bar | CH | 100g |
P002 | Raising the Bar | CH | 200g |
P015 | Anapoppers | SO | 500g |
P016 | Juicy Lucy gummies | SO | 100g |
Assuming, the Product -> Size is a 1-to-many relationship, what would be the guidance in terms of the design and setting?
E.g. Above items having more than one size.
Solved! Go to Solution.
Assuming you have one to many relationship for Products to Size, there can be two cases
Case 1- If your codes differ for each Product Name
Then You will have to make this as a numbered list and you can work on this list based on the codes
Case 2 - Names & codes are same
Then You will have to think of coming up with the unique code for each combination.
You can also think of creating a hierarchy based on the Size & Products
You can also ponder on reversing the list meaning Keep Size as a list and add Product Codes and Names as a attributes
All this depends on what is your final objective and you design accordingly.
Hope that helps
Misbah
Hi @Star
I would concur with @Misbah when it comes to deciding if your list should be numbered or regular.
I would add a few more thoughts though.