Dodeca Version 7.1.0
June 23, 2016 - Build 5510
This version of the Dodeca Framework uses the .NET Framework, version 2.0, Service Pack 1 and higher on the desktop. The components used in this version of Dodeca are SpreadsheetGear 2012 (18.104.22.168), NetAdvantage 2011, Volume 1 (11.1.20111.2042), Aspose.Cells 22.214.171.124, Syncfusion Essential Studio 11.3035.0.30, and GdPicture.NET 11.0.6.
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.6. 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 are supported and tested on Java 1.6. Both services are known to run on Java 1.7, although extensive testing has not been performed on that Java version.
Fixed Issue [UpdateBinaryArtifact Method] – Semi-colon delimited .csv files converted to comma delimited .csv binary artifacts were missing a small amount of data at the end of the file. #1518
Cascading Enhancement – Prior to this release, cascading support for an Essbase Excel view was limited to a single cascade "template" sheet. Cascading is now supported for any number of template sheets, which are specified and configured using the CascadeSheetConfig setting.
The following view level settings are still supported, but have been deprecated, and the recommended approach is to use the CascadeSheetConfig setting to configure one or more template sheets.
Please note that existing cascade views will continue to work without any changes required.
CascadeSheetConfig supports the same settings as defined at the view level, but at a cascade template sheet level.
Fixed Issue – When relational functionality is used within an Excel Essbase View, non-SQL (i.e. non-database client-side) errors that occur during the relational processing are not reported in the view’s status bar.
Fixed Issue – With client-side logging enabled, the client eventually freezes (i.e. becomes non-responsive). Refer to the version 184.108.40.20606 release notes section titled Request and Response XML Client-Side Logging for additional information on this capability. #1494