Powered By
Submitting to a parent account hierarchy node by division or department, and then submitting without division or department, failed to show the correct error message in the client app. (FC-2484)
Planning was allowing submission against parent hierarchy nodes even if a dimension which is dependent on the hierarchy dimension was in the grid or filtered, potentially resulting in the submission being filtered out when the report re-ran. (FC-2536)
Designer would unexpectedly exit if interaction with the Windows clipboard failed when copying error details. (FC-2531)
If you took the active hierarchy's dimension off the grid, the hierarchy remained active, leading to errors when running the report. (FC-2513)
If a catalog failed validation, Designer starts but wouldn't show the Home dialog or any error message. (FC-2515)
The Edit Variables dialog allowed the deletion of a related member variable which another variable was dependent on, leading to an error on opening the dialog subsequently. (FC-2521)
Editing the value of a related member variable in the Variables dialog didn't always update the filter for that variable. (FC-2529)
In the Edit Hierarchy dialog, when you added a child node to a parent node which had never been expanded, the parent node ended up being selected instead of the new child. (FC-2223)
When you add a new column format, the list now scrolls if required to bring it into view. (FC-2451)
In the Hierarchies dialog, subscribing to a hierarchy from the library would inherit expressions for calculated nodes of the same name from a hierarchy previously deleted in that dialog. (FC-2539)
The Excel Add-In didn't correctly show ampersands in the report name in the title of the filter panel. (FC-2523)
A bug in Excel which causes a temporary misalignment of cells with their column headers when grouping is used has been mitigated by an internal work around. (FC-2524)
The Add-In's dialogs are now attached to the Excel window, so that the dialog is brought to the front when you switch back to Excel from another application. (FC-2389)
An intermittent 'object reference not set' error related to linked filters being updated has been resolved. (FC-2406)
The Epicor API support can now handle templates such as GL Transactions with Subledgers which can generate extremely long join clauses. (FC-2494)
The Joint Venture Partner dimension was not filtering the underlying Directory table using the correct contact role grouping. (FC-2483)
The tenant and environment name associated with a Nextworld data source is now displayed in the Admin web app. (FC-2353)
The Reader did not repopulate schema meta data cache on the server, resulting in slightly reduced report opening performance if the cache wasn't populated by other client apps. (FC-2428)
The ChatBot answer would be truncated if it contained a square bracket character. (FC-2302)
The Resync Planning Schema button appeared in the Connections page of the Admin web app even if it wasn't relevant. (FC-2493)
The activity of scheduled background tasks on the FastClose Server has been spread out some more to reduce any impact on the database and other resources. (FC-2497, FC-2492)
The default log level for a new scheduler worker service has been changed from Warning to Information, so that useful events get logged by default. (FC-2505)