đź’ˇ Context:
In many real use cases, end users need to input a large volume of data manually or via copy-paste from Excel. Once the data is entered, they use “Save using Pattern-Based Allocation” to distribute the values correctly.
However, when the number of data entry cells is high, Board executes the save in a cell-by-cell manner, applying the allocation one cell at a time. This cell-based approach significantly increases the number of operations and can negatively impact performance, especially for large datasets.
🔍 What I observed:
To understand the issue deeply, I analyzed the Data Entry logs and tested a capsule procedure combining data entry and save with pattern-based allocation. The logs confirmed that the process is executed cell-by-cell.
(Attached a sample with 4 cells)
Let’s imagine we have 50+ cells instead — in this case, the current cell-by-cell allocation logic becomes a performance bottleneck.
âś… Feature Suggestion:
Introduce an option for a bulk save mechanism when using Pattern-Based Allocation, similar to the Dataflow behavior.
This means applying the allocation logic in one go over all the intersections concerned by the data entry, rather than calculating allocations per cell.
