Dodeca Version 8.9.0

Fixed Issue: When a Data Audit Log record failed to be inserted after an Essbase update or send operation, the failure was not reported, making it difficult for administrators to detect a gap in the audit trail. The failure is now written to the client log. #2918

Enhancement: The AppliedOLAP.Dodeca.Common client library now multi-targets .NET 10 in addition to .NET Framework 4.7.2, laying the groundwork for future Dodeca clients built on modern, cross-platform .NET. #3906

Fixed Issue: Recent Essbase connections that shared the same server, application, and database, but differed by servlet URL, APS URL, or username, displayed identical entries in the Recent Connections list, making them indistinguishable. Connections whose labels would otherwise collide now include the servlet URL in the label; tooltips also show the servlet URL, APS URL, and username so the connections can always be distinguished. #4460

Enhancement: Added a DataCellDoubleClickPolicy property to the Adhoc Essbase view metadata. When set to ShowDrillthroughReportBrowser, double-clicking an Essbase data cell displays the native Essbase Drillthrough Report Browser, allowing the user to select and execute a drillthrough report defined for the cell’s contributing members. Requires an Essbase server that supports native drillthrough reports (Essbase 21c or higher). #4271

Fixed Issue: For an ExcelEssbase view with fine-grain sheet protection (for example, AllowFormatColumns or AllowFormatRows set to true via the SetProtection method), opening the view in Excel or exporting it to Excel could reset those settings to their Excel defaults. This could cause Excel and Dodeca to report an error similar to the following when collapsing or expanding an outline group on the worksheet: Operation cannot be performed on a protected worksheet. Fine-grain protection settings are now preserved when a worksheet is reprotected with a new password during Open in Excel or Export to Excel. #4361, #4185

Enhancement: Added a tokenizable LoginDialogCaption property to the Essbase and EPM connection metadata. When set, the specified caption overrides the default caption on the login dialog for that connection. #2260

Fixed Issue: When testing a RESTful Essbase connection from the legacy Essbase Connections editor, the test connection dialog received no connection information. Server and client version information is now displayed, consistent with other connection types. #4364

Fixed Issue: For Essbase/EPM Cloud connections that use OAuth, a connection could remain reported as connected at the session level after its access token had expired, causing the expired token to be reused as-is instead of being refreshed. This could cause an operation to fail with an error similar to the following: Unable to login to PBCS due to invalid credentials. #4464

Fixed Issue: If one or more database errors occurred while saving changes for a SQLPassthroughDataSetRange (for example, an INSERT, UPDATE, or DELETE denied by a database permission), they were not displayed; instead, an index exception similar to the following was shown: Index (zero based) must be greater than or equal to zero and less than the size of the argument list. The actual database error or errors are now included directly in the exception message, as well as being displayed in an Excel comment on the affected row or rows. #4298

Fixed Issue: For a SQLPassthroughDataSet query configured with a ClientBased connection method, the row count for each returned data table was not reported back to the caller. Row counts are now reported for the ClientBased connection method, consistent with the ServerBased connection method. #4513

Fixed Issue: In the Configure Tools dialog, selecting a custom tool whose tool-controller mapping is stored in the legacy CustomToolControllers module did not display the mapped tool controller or its arguments. The tool controller and its arguments are now displayed for tools mapped by the module. Selecting a tool controller in the dialog stores the mapping in the tool itself, which is the preferred method of mapping introduced in version 8.5.0. #4407

Fixed Issue: Custom tools whose tool-controller mapping is stored in the tool itself did not function on application-level toolbars or in the Workbook Script Debugger unless the mapping was also present in the legacy CustomToolControllers module. Mappings stored in the tool are now honored, and take precedence over legacy module mappings, consistent with the behavior of view toolbars. #4407

Enhancement: Added an optional DefaultValue parameter to the @PVal(<PropertyName>, [<DefaultValue>]) function. #4497

Fixed Issue: When a workbook script renamed a worksheet during the view build (for example, using the RenameWorksheet method in a procedure attached to the AfterBuild event), rebuilding the view could cause datapoint functions, such as @DPDimValMbr, to return member names from the retrieve of a previous build rather than the most recent build. Internal retrieve range information is now cleared when the existing workbook is closed at the start of a rebuild, so datapoint functions always reflect the most recent retrieve. #4324

Fixed Issue: The @PVal(<PropertyName>) function could fail to resolve with an Error resolving formula message, even when the specified property existed. This failure occurred when it was evaluated from an event link that runs before the view’s workbook has been loaded into its grid control (for example, AfterTokenTableBuild). #4516