Unexpected Behaviour: Data Entry with Pattern Base Allocation

Matteo.Anniciello

Good day everybody!

I’m experiencing an unexpected behavior with Pattern Based Allocation (PBA) in a Data View.

I’m using PBA to enter a value at an aggregated level into a target cube (initially empty) and allocate it down to a more granular level using another cube with the same structure (driver cube).

The issue is that data entry works correctly as long as I have a maximum of two Entities by Row, but as soon as I add a third Entity by Row, the data entry stops working: the entered value disappears after saving and nothing is written back to the cube.

What’s strange is that if I first select the cell/row in the Data View (so the context is narrowed) and then enter the value and save via PBA, it works as expected.

Does anyone know what could cause this (e.g., allocation scope becoming too large, refresh/trigger settings, or a known limitation/bug), and what the recommended workaround or design pattern would be?

Board Version: 12.6

Vishwajit Rajput

Hi @Matteo.Anniciello ,

This behavior is related to how Pattern-Based Allocation resolves the dimensional context of the entered cell.

When multiple Entities are set by row (especially 3 or more), the cell where the value is entered may represent several possible combinations. In that situation I think, Board cannot determine a unique allocation scope for the PBA, so the entered value is discarded when saving.

When you first select the row, the selection narrows the context to a single combination of the row entities, allowing the Pattern-Based Allocation to resolve correctly and save the data.

A common workaround is to reduce the allocation scope by moving one of the entities to a Pager or Selector, or by handling the allocation through a procedure (“Save Data Entry using Pattern-Based Allocation”) instead of direct Data View entry.

Thanks!