Hi Community,
I’d like to share a slightly complex use case that might open a discussion on potential improvements or clarifications around how dynamic selections work in Board.
🎯 Context:
I have an entity called Month
, which has two parents:
Month of the Year
→ contains values like January, February, etc.Year Period
→ contains values such as Y-1, Y, Y+1 to indicate the year to which the month belongs (Grand parent)
✅ Expected behavior with fixed selection:
When I manually select:
Month of the Year
= JanuaryYear Period
= Y-1
I correctly get January 2024, which is expected.
❌ Issue with dynamic selection via cube:
However, when I try to reproduce the same logic using dynamic selections from cubes (one cube for Month of the Year
and another for Year Period
), Board seems to only keep the last applied selection.
That means the cross-filtering between the two parents is not respected, and only the latest parent selected dynamically is taken into account. I assume this is due to some internal logic or priority handling in the selection engine.
🔄 Working workaround:
I’ve found a workaround using a procedure with two steps:
- Apply Dynamic selection from cube on
Year Period
- Apply Dynamic selection from cube on
Month of the Year
- Use
Go To Screen + Apply Selection to Screen
Surprisingly, this allows me to simulate a working dynamic selection across two parents.
Even more interesting: if I copy the selection from the screen where the procedure applied it and paste it into another screen and save, it works both parent are selected dynamically based on cubes .
❓ My questions:
- Can this kind of "forced" dynamic selection have any side effects?
- Could someone explain more precisely what happens in the backend when multiple parents of the same entity are selected dynamically based on cube ?
- If it’s a matter of selection order, could Board consider enhancing this by:
- Respecting the order in which cube-based selections are applied in the same selection pop up?
Thanks in advance for your insights!
Akrem