Dodeca Version 8.2.1
January 6, 2023 - Build 253
This version of the Dodeca uses the .NET Framework, version 4.7.2 and higher on the desktop. The components used in this version of Dodeca are SpreadsheetGear 2017 (220.127.116.11), NetAdvantage 2021, Volume 2 (21.2.46), Aspose.Cells 22.5.0, Syncfusion Essential Studio 18.104.22.168, GdPicture.NET 22.214.171.124, and Xceed Zip 3.6.7363.15420.
This version of Dodeca has two server-side services that run inside a Java Application Server. The Dodeca service is supported and tested on Java 1.8. The Dodeca-Essbase service for all Essbase versions prior to, and including, Essbase 126.96.36.199 are supported and tested on Java 1.5. The Dodeca-Essbase service for all Essbase versions 188.8.131.52 and higher is supported and tested on Java 1.6. Both services are known to run on Java 1.7, 1.8, 1.9, and 1.10.
The release notes for this version contain the following sections:
Authentication Services - LDAP Authentication Services
Fixed Issue: When connecting to an LDAP server, Dodeca constructs a network credential for the user with the Windows logon domain. If the Windows logon domain differs from the domain of the configured LDAP server, the connection can fail or incorrect group information can be returned. A new
LDAPCredentialDomainPolicyproperty has been added to the LDAP connection properties to allow for a credential to be constructed without using the Windows logon domain. #3287
Fixed Issue: When the
ListSourceTypeof an auto-complete range is DelimitedString, and each string in the
DelimitedStringvalue is specified on a separate line in the Editor, only the first string is presented in the auto-complete dropdown list in the worksheet cell. #3315
Fixed Issue: When the user enters blanks as the accepted value, the value is not detected as invalid. #3290
Fixed Issue: When a view contains auto-complete ranges, closing the view window may cause the application to abort and display the following error: WorkbookView has been disposed. This issue was introduced in 184.108.40.2063. #3283
Fixed Issue: When an Excel Essbase view is configured with multiple cascade sheets, only the data set ranges that apply to the first cascade template sheet are retrieved. #3349
Fixed Issue: In the Comments Editor, the Chat style user-interface window does not use all of the available horizontal space before wrapping. #3253
Fixed Issue: In the Comments Editor, the Grid style user-interface does not allow the Subject to be edited. #3330
Fixed Issue: When a comment range’s
InCellDisplayPolicyis MostRecent, and a comment is already associated with a given cell, when another comment is entered and saved from the Comments Editor, the cell in the sheet is not automatically updated to reflect the most recently added comment. When the view is rebuilt, the sheet cell does contain the most recently added comment. #3268
Fixed Issue: When
AllowAttachmentsis enabled for a comment range and the sheet range contains more than 1000 cells when using Oracle as the metadata database (or more than 2100 cells when using SQLServer), an error occurs when the view is built. #3338
Oracle error: ORA-01795: maximum number of expressions in a list is 1000
SQLServer error: The incoming request has too many parameters. The server supports a maximum of 2100 parameters. Reduce the number of parameters and resend the request.
Dodeca Metadata Service in Load Balanced Environment
Fixed Issue: When the Dodeca metadata service is used in a load balanced environment, changes to metadata are not reflected by all servers within the environment. As a consequence, changes made by a developer are not available to all clients. #3355
Fixed Issue: When Oracle is used as the metadata database, the following error occurs with the
delete-metadata-audit-log-records --days <# of days>command: org.hibernate.exception.DataException: could not execute statement #3297
Fixed Issue: When the TENANT_CONFIG
TokenDurationSecondshas not been explicitly configured in Dodeca Shell, an Error executing client request occurs when an SSO token is being created by the metadata server. #3242
Fixed Issue: When multiple Essbase drillthrough reports are available for a given cell or cells, an error similar to the following occurs when the user double-clicks to open the drillthrough report: Unable to get the Linked Objects Browser. Unable to construct the user-interface component object type "AppliedOLAP.Dodeca.Essbase.Windows.Common.DrillthroughBrowser". […] This issue was introduced in Dodeca 220.127.116.114. #3274
Essbase Unknown Members
Fixed Issue: When multiple ranges are retrieved by a view that has the
ParallelExecutionproperties set to True and at least one of the retrieved ranges contains an unknown member, attempting to display the Unknown Members Explorer can result in an error similar to the following: Unable to update Unknown Members Explorer. Index was outside the bounds of the array. #3312
Fixed Issue: When the Export Metadata to Local Zip File utility is used and an existing file is selected, the user is prompted with "<file name> already exists. Do you want to replace it?" The issue is that when the user clicks Yes, the exported metadata is added to the existing zip file instead of the file being replaced with a zip file that contains only the currently selected metadata instances. #3189
Fixed Issue: When the Import Metadata from Local Zip File client utility is used to import metadata that already exists in the metadata repository, the original Imported Date value is cleared in the databaase and the current date is not assigned as the new value. As a result, no Imported Date is retained in the database. #3357
Fixed Issue: When the Dodeca Shell
import-tenantcommand is used to import metadata and the
--import-userflag is not used to specify the Imported By user, the Imported Date is not presented in the Import Metadata from Local Zip File and Export Metadata to Local Zip File utilities in the client. #3356
As a best practice, it is recommended that when importing metadata using Dodeca Shell, that the
--import-userflag be used to provide an indication of who imported the metadata.
Metadata Dependency Explorer
Fixed Issue: The Metadata Dependency Explorer does not detect an application’s dependency on the view specified as the
Fixed Issue: The Metadata Dependency Explorer does not detect a
SQLPassthroughDataSetHierarchyselector list’s dependency on the SQLPassthroughDataSet specified as the
Fixed Issue: In the Module Editor, when a new module is created and files are added to the module, and then committed, the files are not retained and must be re-added to the module and then re-committed. #3292
Open In Excel
Fixed Issue: When a view’s caption contains a forward slash and/or backslash, the following error occurs when the Open In Excel tool is used to open the view in Excel: The process cannot access the file "<file name>" because it is being used by another process.
In 8.2.1, all invalid filename characters, which include the forward slash and backslash, in the view’s caption are replaced with an underscore to construct the file name. #3318
Fixed Issue: In a previous 8.x release, the Open In Excel tool was modified to replace all non-alphanumeric characters in the view’s caption with an underscore when constructing the Excel file name. This is for security reasons, but the approach has been slightly revised to retain blank characters. So, any blanks in the view’s caption are retained in the Excel file name. #3336
Fixed Issue: When opening a PDF in the system’s default viewer with the Open in External Viewer tool, an error similar to the following is displayed: Unable to open "<file path>" in an external viewer. Unable to create the PDF file "<file path>". This issue was introduced in 18.104.22.1689. #3343
Fixed Issue: The PDF navigation tools for moving to the first, last, previous, next, or specified page do not work. This issue was introduced in 22.214.171.1243. #3342
Fixed Issue: Opening a PDF view can cause the application to rescale incorrectly on high DPI monitors. This issue was introduced in 126.96.36.1999. #3344
Added support for rendering additional document formats, notably
In versions prior to 8.2.1, a saved Essbase adhoc view, when opened, did not restore sheets that had been added by the user before saving the view, so only the first sheet was available when the saved view was opened. This issue has been addressed in 8.2.1. #3353
In addition, the information that is retained in a saved adhoc view has also been revised, such that all changes by the user, including formatting, formulas, etc. are persisted with the saved view and restored when the saved view is opened.
In 8.2.1, workbook scripting can be used to import an Excel binary artifact into an Essbase adhoc view in the
AfterTokenTableBuildevent when the view is building. This allows for an Excel template to be loaded by an adhoc view in order to provide an initial member layout. While this approach mimics the behavior of an Excel Essbase view, the caveat is that any changes to the Excel template will not be preserved when a saved view is opened.
The following is an example of a workbook script that imports an Excel binary artifact into an Essbase adhoc view.
The OnAfterTokenTableBuild procedure exits the procedure when the view is a saved view to avoid loading the template into an opened saved view.
The default workbook contains a single sheet, Sheet1, which is renamed before importing the Excel binary artifact, since the only sheet cannot be removed.
The BinaryArtifactOperations.ImportWorkbook overload copies all the sheets in the specified Excel binary artifact into the current workbook.
The original renamed sheet is removed.
Fixed Issue: When a query’s
UpdateSQlcalls a stored procedure, and the casing of the characters in the column names specified in the stored procedure differs from the column names in the SelectSQL statement, the delete, insert, or update operation is not performed at runtime, and no error is reported.
While this issue has been addressed in 8.2.1, the recommended best practice is to always use the exact columns names in stored procedures and in the statements that match the casing of the column names as defined in the database. #3277
View Hierarchy Editor
Fixed Issue: When the Insert View dialog is opened from the View Hierarchy Editor, the first item is highlighted, but not selected, which is misleading. If the first item represents the view to be inserted, the user must manually select the item. #3261
Fixed Issue: When an application’s
ViewSelectorObjectTypeIDis set to ViewSelectorExplorerBarTreeHybrid, and the view hierarchy contains a view as a root node, the context menu is either not displayed when the view is clicked with the right mouse button, or the context menu for another view that was most recently displayed, is displayed instead. #3254
View Usage Viewer
Fixed Issue: When the build of a view fails due to a workbook script error, the raw XMl is written to the View Usage Log and presented in the View Usage Viewer as the Build Error. In 8.2.1, the error is logged and presented as readable text instead of XML. #3111
Workbook Analyzer Utility
In 8.2.1, a Help "?" button is available for the Removed Defined Names where field. When clicked, the Where Syntax Help is opened. #3276
Workbook Script Debugger
In the Workbook Script Debugger, when the user clicks the Formula Evaluator tab caption to open the tab or the tab is already open and visible, the value of the selected method argument in the Breakpoints tab is automatically shown in the Formula field. #3224
Fixed Issue: An error similar to the following occurs when the Workbook Script Debugger is open during the
BeforeRangeRetrieveevent for a view that contains multiple retrieve ranges, and any of the retrieve ranges does not use the view’s Essbase connection: #3308
Unable to build the view. Unable to retrieve the view data. Unable to retrieve sheet "Sheet1". Unable to retrieve range "Sheet1!Ess.Retrieve.Range.2". Unable to retrieve range "Sheet1!Ess.Retrieve.Range.2" on sheet "Sheet1". Member [PD900001B] is out of place
Workbook Script Editor
Fixed Issue: In the Formula Editor, when the user attempts to insert a Dodeca function immediately prior to another Dodeca function by typing the
@symbol, the text insertion cursor jumps to the end of the second function and the context choice menu is not displayed. #3351
Fixed Issue with Workbook Script Trace Logging: When a Dodeca application is launched as a user without a documents folder (such as the sytem account), the application can get caught in an infinite loop and hang indefinitely. #3339
Fixed Issue with
RangeSelectionChangedevent: When a procedure is associated with the
RangeSelectionChangedevent link, the procedure can be executed more than once each time the range selection changes. This issue was introduced in 188.8.131.523. #3348
Fixed Issue with
@Path()function: When the
@Path()function is used to perform a CleanPath operation, invalid file characters are removed rather than only invalid path characters. In 8.2.1, only invalid file path characters are removed. #3329
Fixed Issue with
RenameWorksheetmethod: When the SheetToRename and NewSheetName arguments have the same value (i.e. a sheet is being renamed to the current name), ' (1)' is added to the sheet name. #3320
Fixed Issue with
SendEmailmethod: When any of the
AttachViewmethod arguments is True and the view’s
CaptionAfterBuildproperty is set, the caption is not used as the name of the attachment. #3296
Fixed Issue with
SetRowHeightmethod: The MinHeight argument is not applied when CellByCell is not used. #3321
Fixed Issue with
WriteLogMessagemethod: When the specified Filename does not include the file extension, the following error occurs: WorkboookScriptClasses_Invalid_folder_or_filename #3275
Fixed Issue with
Rangeoverload: An error similar to the following occurs when the sheet name contains a single quote or special character: Unable to retrieve range on sheet "Sheet'1". "Ess.Retrieve.Range.1" is not a valid range name. #3305
Fixed Issue with SpecifySheetsBy.AllSheets execution in asynchronous views: When adding, removing, or rearranging worksheets via a method with the SpecifySheetBy argument set to AllSheets, an illegal sheet index exception can occur. #3327