Hi everyone,
I’m struggling with a time hierarchy design in BOARD and I’m hoping the experts here can help me crack it !
Context :
In BOARD, relationship logic is N → 1, which normally works fine…
BUT in my case I need to introduce a Bimonth entity (every 2 months).
So for a standard calendar year:
- 12 Months
- 6 Bimonths (Jan–Feb, Mar–Apr, …)
- 4 Quarters
- 1 Year
📌 The Challenge
I need both of these relationships at the same time:
- Bimonth → Year
- Quarter → Year
But if I establish:
- Month → Bimonth
- Month → Quarter
- Quarter → Year
- Bimonth → Year
…I end up with circular relationship problems because Quarter and Bimonth both ultimately aggregate the same Months to the same Year.
How should I define the custom time relationships so that I can have both Bimonth and Quarter linked to Year — but without triggering circular dependency errors?
Has anyone already implemented multi-granularity time aggregations (Month → Bimonth and Month → Quarter) leading to the same Year entity in BOARD?
What modeling workaround did you use?
Thank you all very much for your guidance !
Anis
