Powered By
The performance of logging in has been improved, in many cases by several seconds. (FC-3698, FC-3699)
Elimination of sql windowing functions from a number of FastClose views reduces some report runtimes.
When changing a filter selection to a range which refers to a calculation and a code which doesn't exist, an unhelpful error message would appear. (FC-3162)
If only a calculation was selected in the filter for a dimension in the down axis, the report results incorrectly included all other members of that dimension as well. (FC-3286)
In the Edit Member Captions Expression dialog for a Calculated Field, an added dimension was always inserted at the start of the expression instead of where the cursor was. (FC-3591)
In rare cases, errors communicating with Excel when displaying report results could cause the add-in to retry indefinitely, locking Excel. (FC-3550)
An error would occur when saving a workbook containing a drill through target report. (FC-3700)
If a cell format would have been applied to a rectangle ending with column Z, it would get applied up to column AZ instead. (FC-3731)
It was possible to accidentally link variable filters of different types in the Linked Filters dialog, such as Scenario (text) with Period (number), which could subsequently result in errors. (FC-3740)
In certain circumstances an error on running the report would be logged but not displayed to the user, who would just see no results. (FC-3741)
Drilling to a target report wasn't passing members in filters for dimensions which were neither across nor down. (FC-3733)
An error could occur on searching for a report. (FC-3732)
An unnecessary 'Task cancelled' message was displayed if planning submission was cancelled by the user in the Excel Add-In. (FC-3695)
An error could occur when the workflow results page of the Admin app was refreshed. (FC-3737)
An unnecessary 'task cancelled' error was being logged by the Admin app if the worker service wasn't available. (FC-3694)
Fields required by calculated columns in FastClose views based on the * operator were not getting added to the subquery, causing a Bad BAQ. (FC-3744)
If the Nextworld API says that a query had to be cancelled because it was taking too long, that should be logged as a warning not an error. (FC-3584)
Added Intrastat cube to AR module.
Internal
Avoid explosion of Role Names in Application Insights (FC-3701)
Ensure EnsureRepositoryIsLicenced is pushed onto ThreadPool (FC-3703)
Ensure that the automatic Application Insight events are enriched properly (FC-3704)
Application insights no longer logs the SQL query (FC-3681)