New accoPLANNING release: v1.1.2.5

Version 1.1.2.5 brings the following fixes and improvements
New Features
Custom Excel Export
A fully rebuilt Excel export now reconstructs the pivot table's cross-tab layout directly — matching exactly what is shown on screen, including your row and column hierarchy groupings and all visible measures. Subtotals and Grand Total rows are included and marked in bold. Previously the export relied on Flexmonster's internal rendering which could produce inconsistent results for certain hierarchy and measure configurations.
Per-Measure Lock Column Assignment
Each measure in your report can now be individually configured to use a specific lock column (or none at all). A "Lock measure" dropdown appears in the Cell locks formatting pane for every bound measure, replacing the older all-or-nothing approach. Reports configured before this version continue to work unchanged; existing lock column assignments are automatically migrated on first load.
A "Writeback column name" field is also available per lock column, letting you override the database column name used when writing lock state back without renaming the field in your data model.
Bug Fixes
Shadow calculations in batch-row mode:
 Calculated fields (shadow calculations) whose output targets overlapped with other pending edits could retain stale delta values when saving in batch-row mode. This is now resolved — all calculation output targets are included in the delta merge on save.
Exclude Zeros with multiple measures:
 When "Exclude Zeros" was enabled and an entry had one measure edited to a delta of zero, that edit entry could be incorrectly dropped even if other measures on the same row still had non-zero delta values in the same entry (like when using Shadow calculations). The check now considers all measures before dropping an entry.
Delta merge with multiple pending edits per row:
 When multiple pending edits existed for the same data row (e.g., after several unsaved changes), the delta merge in batch processing could apply an incorrect base value for later edits. This is now fixed.
Checkbox rendering:
 In certain configurations, boolean/checkbox cells could render with a checked="null"
 HTML attribute — which HTML treats as truthy — causing checkboxes to appear checked regardless of their actual value. Fixed to emit an empty attribute string instead.
Comment input type in mixed-type rows:
 In rows where a measure can be either numeric or text, comment input fields could incorrectly receive a type="number"
 or type="checkbox"
 attribute, breaking text entry. The input type is now always forced to text
 for comment fields.