Powered By
Row based formatting, typically used by hierarchies and subtotal rows, is applied much more quickly when report results are displayed. A test case report with several thousand subtotal rows formatted in bold was improved from 236 seconds down to just 7 seconds. (FC-3671)
Re-running a planning report which contains a large number of formulas or unsubmitted values in planning cells is significantly faster. (FC-3683)
Opening a workbook which has many planning cells within its worksheets is much faster. In one test case with 11,000 planning cells, the workbook opening time was improved by 18 seconds. (FC-3672)
A report which aggregates a column which is defined as a calculation in the catalog would intermittently error on run when using a 3 tier ERP connection. (FC-3669)
If an error occurred while opening the Calculation Dependencies dialog, Designer would unexpectedly quit. (FC-3688)
While the Excel Add-In is running a report, the buttons in the FastClose tab of the ribbon are disabled, as their operation could be unreliable. Filters are also disabled, as changing selections would have no effect on the eventual result and would result in contradiction. (FC-3677)
The Excel Add-In now provides feedback during planning submission, via the filters task pane, and the ability to cancel the process. (FC-3678)
Cancelling a report run in the Excel Add-In resulted in an unnecessary message saying 'Task was cancelled'. (FC-3682)
Border formatting was being applied to regions rather than each row. For example, if two subtotal rows were adjacent, only one of them would receive a top or bottom border. (FC-3674)
Interaction with Excel is no longer blocked during planning submissions, so it doesn't say 'Microsoft Excel is waiting for another application to complete an OLE action' after 90 seconds or error if you click Cancel at that point. (FC-3673)
A report saved with column subtotals on the Scenario dimension would error when re-opened. (FC-3676)
An intermittent error that could occur on editing a Dimension Security rule in the Admin app has been fixed. (FC-3667)