Use combined lists ou other parent child relation?

[Context Demand Planning for school books]
I have 5 lists:

SKU (Book) - e.g:5858595
Subject - e.g. Maths
School Year - e.g 5º Grade
Type of Subject (Mandatory/Not Mandatory)

Theoretically, each subject has two parents: The type of subject and the school year. Since it is not possible I thought of 2 possible designs:

A simple child parent relationship
Sku > Subject > School year

Problems:
- There are subjects that are common to more than one year (e.g Math's 5º Grade & Math's 6º Grade), so it implies that the name of each subject is "Subject - Year ; e.g Maths 5º Grade"
- I can not map the type of subject as the parent for the subject and therefore, when filtering there will be nonsense combinations (it would be possible to select "Non-mandatory" in the filter "Type of Subject" and select a mandatory subject in the filter "Subject")

2) Create combined list that combines school year and subject and use this as a parent of the SKU

Sku > Combined List > Type of subject

Can you help me understand what option better fits my problem? Are there other solutions?

Thank you so much for your time.

Accepted answers

All comments

anirudh

Hi versilva

Would you mind providing more context? Wouldn't the property of the book be the subject? Why would the same SKU 5858595 roll up to more than one subject

If the SKU has the subject as a line item against a module, then the Mandatory and Non Mandatory can work via a lookup and also function as a property. Here's a screenshot demonstrating that:

and the mapping module:

Not sure that this is entirely helpful, let me know what you think!

versilva

Hi Anirudh
Thank you so much for your help and attention

Trying to explain myself a little better:

1) This are the relationships:

- Each SKU roll up to : only one subject;
only one school year
only one type (mandatory or not)

- Each Subject roll up to : multiple school years
multiple types (mandatory or not), according to the school year as I wrote below

- Each combination Subject - School year rolls up to only one type (Mandatory/Not mandatory)

1) Wouldn't the property of the book be the subject?
Are you suggesting I should define the subject using property instead of a parent child relation? Why would this work better?

2) Why would the same SKU 5858595 roll up to more than one subject ?
Indeed a SKU does not roll up to more than one subject

3) If the SKU has the subject as a line item against a module, then the Mandatory and Non Mandatory can work via a lookup and also function as a property.

My struggle is that if I do not have a parent child relationship when I want to filter by school year/subject and type(mandatory), there will be combinations that do not exist ( Math's + Non mandatory), which doesn't make sense for the analysis.

anirudh

So for filtering via properties have you tried this kind of dropdown based filter? It does not require any specific style of hierarchy!

Here is the view without any filters

And if I filter on Math and 5th Grade

Or filtering on all 3 properties

Or do you need the change in hierarchy for reasons other than filtering

Quick Links

Can you help?

Unanswered questions

Different Subsets of Parent Lists in Input & Output Modules
I have 2 lists used in modelling, In Input module I'm using subset of territories from Country List and subset of Regions from Flat list. But in Output module,Its reversed, I'm using subset of regions from Country list and subset of territories from flat list.How to derive the numbers from input to output module. I do have…
Is there a way to turn off the Show Comments Summary panel in UX pages with Comments?
This shows all comments across all data to all users with access to the UX page. This is not appropriate for any UX which might contain security access sensitive data. Comments on grids and cards ARE security dependent. That works fine. But anyone with access to the page can open this Summary Panel and see ALL comments…
Are there any plans to support actions to rename or delete native Versions?
If anyone is aware of idea exchange ideas that are currently being evaluated by the product team, if you don't mind linking them here, would love to give them an upvote. Thanks!