While transitioning and testing our application from the Windows GUI to the Universal GUI, we noticed a fundamental difference in how Default logic executes during a data import.
In the Windows GUI, the @cursor_from_col_id parameter always remains empty (NULL) during an import (where @import_mode > 0), evaluating exactly once per row.
In the Universal GUI (via Indicium), @cursor_from_col_id is populated sequentially with the Column IDs currently being processed by the OData Import API. This causes the Default logic to fire multiple times per row.
While we understand this stems from the architectural shift to Indicium's server-side processing framework, it breaks or causes unexpected side effects in our existing SQL logic.
We would appreciate your insights on the following:
- Is this specific behavioral discrepancy documented or mentioned in any specific whitepaper?
- What is the best practice for structuring Default logic so that it handles imports predictably via Indicium?