BusinessObjects Extended
Analytics 4.1 Release Notes
Patents Business Objects owns the following U.S. patents, which may cover products that are offered
and sold by Business Objects: 5,555,403, 6,247,008 B1, 6,578,027 B2, 6,490,593 and
6,289,352.
Trademarks Business Objects, the Business Objects logo, Crystal Reports, and Crystal Enterprise are
trademarks or registered trademarks of Business Objects SA or its affiliated companies in the
United States and other countries. All other names mentioned herein may be trademarks of
their respective owners.
Copyright Copyright © 2007 Business Objects. All rights reserved.
Third-party
Contributors
Business Objects products in this release may contain redistributions of software licensed from
third-party contributors. Some of these individual components may also be available under
alternative licenses. A partial listing of third-party contributors that have requested or permitted
acknowledgments, as well as required notices, can be found at:
http://www.businessobjects.com/thirdparty
BusinessObjects Extended Analytics 4.1 Release Notes
Contents
1
Overview .................................................................................................................................4
2 What’s new in this version?....................................................................................................... 5
2.1 New functional features...................................................................................5
2.1.1 Designer ................................................................................................ 5
2.1.2 Analyzer.................................................................................................8
2.1.3 Reporter............................................................................................... 10
2.1.4 New in the documentation................................................................... 10
2.2 New technical features .................................................................................. 10
2.2.1 New server component: Configuration Manager................................. 10
2.2.2 Architecture ......................................................................................... 10
2.2.3 Platform evolution................................................................................ 10
3 Migration, best practices & implementation ............................................................................11
3.1 Solution migration.......................................................................................... 11
3.2 Calculated members, MDX formulas............................................................. 11
3.3 Single measure.............................................................................................. 11
3.4 Internal identifiers for Finance dimension members...................................... 11
3.5 Period dimension type...................................................................................11
3.6 Hierarchy level relationships..........................................................................11
3.7 Migrating reports in Excel 2007.....................................................................12
|
4 Technical platform changes .................................................................................................... 13
5 Language and terminology changes.......................................................................................13
6 Appendix – Corrections......................................................................................................... ..14
6.1 Designer.........................................................................................................14
6.2 Deployer.........................................................................................................17
6.3 Reporter......................................................................................................... 17
6.4 Security.......................................................................................................... 18
6.5 Translation.....................................................................................................18
3
BusinessObjects Extended Analytics 4.1 Release Notes
|
Overview
1 Overview
The BusinessObjets Extended Analytics release note contains:
• The new functional and technical features added to the released version
• The most important information about the migration process, best practices and
implementation
• The technical platform changes for the released version
• The language and terminology changes for the released version
• A list of the corrections made to the previous version
This section outlines the corrections made in this version of the software. Each
correction has been given an ID (BOEA for BusinessObjets Extended Analytics) and a
number.
Warning - Do not confuse this internal reference with the Support HelpDesk reference.
You should consult the following documents before you install or migrate to this version. They
are available in the About folder of the installation CD.
Document Description Language
Release note
Document Description Language
Architecture and
recommendations
Installation guide
Administration guide
Event log
You can install the online help using the installation CD and access it via the product interface.
Note - A description of the contents of the CDs delivered with this version is available in the
Installation guide.
List of improvement requests and corrections
made
Technical architecture and hardware and
software configuration details
How to install and configure the product English
Information about the product’s administration English
Description of the main errors generated in the
technical log
English
English
English
4
BusinessObjects Extended Analytics 4.1 Release Notes
2 What’s new in this version?
2.1 New functional features
2.1.1 Designer
2.1.1.1 Copying and pasting a view in a solution, and a deployment in a view
It is now possible to copy and paste views and deployments directly from the Administrator
user interface. You can also copy and paste a deployment in a view.
The principle is the same as for Windows folders in Windows Explorer.
2.1.1.2 Deleting solutions
Previously, the only way to delete solutions was to access the Analytics Solutions tables stored
in Finance. This new functionality enables the end user to delete solutions directly from
Administrator.
|
2.1.1.3 Hiding excluded dimensions
The end user can now hide or show the excluded dimensions that will not be deployed in the
cube.
2.1.1.4 Merging dimensions
In previous versions of Administrator, only the following dimensions could be merged: Variant,
Data entry period, Consolidation currency, Category, Scope.
In version 4, any combination of dimensions can be merged. The resulting merged dimension
members can be renamed.
2.1.1.5 Automatically selecting members added in BusinessObjets Finance
The new option ‘Select all members’ enables you to automatically select in BusinessObjets
Extended Analytics Designer the newly added members in BusinessObjets Finance.
2.1.1.6 Choosing the aggregation when excluding a dimension
As a consequence of the new ‘Select all members’ option, when you choose to exclude a
dimension, you no longer need to select either of the following two options: ‘Aggregate selected
elements’ or ‘Aggregate all elements’. You simply select the ‘Select all members’ option or
manually select the members.
2.1.1.7 Deploying single measures
In the previous versions, you could use multi-measures. Single measure mode is now
available. It enables you to view all detailed and non detailed data on the same measure.
The multi-measure mode is the default mode.
Please refer to the “Migration, best practices & implementation” chapter of the current
document.
2.1.1.8 Deploying both fiscal and calendar time hierarchies
Both fiscal and calendar presentation of data are now available. This presentation mode can
also be applied to the data entry period hierarchies.
For a fiscal hierarchy, the starting period can be different from January. Time aggregations will
be calculated based on this new starting period.
5
BusinessObjects Extended Analytics 4.1 Release Notes
|
What’s new in this version?
It is now also possible to select the number of Periods and Data entry periods directly in
BusinessObjets Extended Analytics Designer.
2.1.1.9 Creating SSAS attributes based on BusinessObjets Finance characteristics and
properties
Before version 4, Finance characteristics were interpreted as hierarchies only. The only way to
retrieve information based on characteristics was to deploy these hierarchies in the cube.
It is now possible to load the cube with BusinessObjets Finance characteristics or properties
that are treated as attributes. The benefits are:
• Ability to perform advanced selections based on attributes and filtering expressions,
such as: is / is not, combined conditions.
• Presentation enhancement, such as the ability to create a calculated description of a
member plus a characteristic.
The attribute name can be customized by the user to fit with OLAP analysis needs.
2.1.1.10 Defining default number format
You choose the default number format that will be taken into account in the entire SSAS cube.
A set of predefined formats is proposed, but you can enter custom number formats.
This format is defined at the deployment level, enabling you to apply different formats to
different deployments.
2.1.1.11 Adding comments to calculated members
You can now enter comments to keep track of what issue the calculated members are
designed to resolve, such as content.
2.1.1.12 Using your own MDX scripts for a deployment
You can now use your own MDX scripts in BusinessObjets Extended Analytics Designer. A
script will therefore be attached to a specific deployment and will be deployed along with the
cube.
An MDX script is saved as a custom calculated member.
2.1.1.13 Creating SSAS named sets based on BusinessObjets Finance characteristics
and filters
You can now create SSAS Named sets from BusinessObjets Finance characteristics, filters, or
any manual selection.
A Named set is a selection of dimension members that will be used as a flat list to create
reports. It is the equivalent of BusinessObjets Finance filters.
2.1.1.14 Deploying several BusinessObjets Finance descriptions for each dimension
member
You can now customize descriptions to satisfy analysis requirements.
This new functionality is important because: from the data retrieval applications, end users
want to be able to display metadata with different formatting (for example, for codes and
descriptions). For instance, a controller is used to working with codes while other users want to
publish reports with short descriptions.
2.1.1.15 Including the NA member in a dynamic selection for detailed dimension
members
In the previous versions, you could include for each detailed dimension, the NA member only
when using the manual selection.
You can now include the NA member in a dynamic selection, which is a selection using
BusinessObjets Finance filters or characteristics.
6
BusinessObjects Extended Analytics 4.1 Release Notes
2.1.1.16 Updating a deployment
It is now possible to update a deployment.
The following items will be updated:
• Calculated members
• Named sets
• Live access settings
2.1.1.17 Enabling aggregation on hierarchies
It is now possible to activate or deactivate the aggregation on nodes independently for Parent
Child and Named level hierarchies. The ‘Dimension supports aggregation’ option has been
replaced by two new options.
Concurrently, for aggregatable hierarchies, it is now possible to deactivate the calculation at
the “All” node level when not relevant.
2.1.1.18 Enabling automatic aggregations on the Period and Data entry period
dimension hierarchies
You can choose to apply a different behavior on time aggregation by activating the automatic
time aggregation based on BusinessObjets Finance flow types.
|
2.1.1.19 Loading external data into BusinessObjets Extended Analytics cube
It is possible to load data not stored in BusinessObjets Finance directly into the cube.
2.1.1.20 Language mapping between BusinessObjets Finance and BusinessObjets
Extended Analytics Designer
In the Languages tab when you select Tools>Options, you can fill in the Culture column (it is
already filled in by default). The culture information is to be used when deploying the cube. It
enables you to specify for example “en-us” for the English language in the US. You must use
the appropriate syntax, adhering to the 639-1 and 3166 ISO norms.
The keys defining the languages culture have been deleted from the configuration file.
2.1.1.21 New keys in the Configuration file
You can modify the following new keys in the Configuration file, which is the
'Cartesis.InformationDelivery.Workbench.exe.config' file:
• "IsAccountDimensionAggregatable". This key is linked to the aggregation calculation
for the Account dimension. The default value of this key is "false". If you set the
value to "true", the aggregation will be available for the Parent Child Hierarchy option
of the Account dimension.
• "MergeMemberMaxDisplay". This key is linked to the number of members you can
display in Designer for each merged dimension. By default, you can display 5000
members. You can change this number by changing the value of the key.
• "MultiMeasureGroupAnalysis". This key is linked to the multi- and single measure
modes. By default, the value of the key is
is activated. You can change the value to "false" if you want to activate the single measure
mode.
"true", meaning that the multi-measures mode
2.1.1.22 Deleted keys in the Configuration file
The following two keys have been deleted from the Configuration file, which is the
'Cartesis.InformationDelivery.Workbench.exe.config' file, since the start and end date for
periods are now defined in Designer interface.
• "MinDisplayDate"
• "MaxDisplayDate"
The following key has been deleted since it is no longer required with the batch functions
starting with version 3.5.
• "GenerateStarSchemaScripts"
7
BusinessObjects Extended Analytics 4.1 Release Notes
|
What’s new in this version?
2.1.1.23 Default member selection
In Designer 4.0, default members were selected by right-clicking on dimension hierarchies. In
Designer 4.1, default members are selected via a new button in the default member editor (see
following screenshot).
Only dimension members that are present in all selected dimension hierarchies can be
selected as default members. Consequently, dimension members present in only one of the
selected hierarchies are not displayed. Furthermore, if the "Suppress dimension members"
function is activated on one of the selected hierarchies, the "All" dimension member is the sole
choice of default dimension member.
If there is no default member selected in the default member editor, the "All" dimension
member is automatically selected as default member of the dimension. If the "All" member
does not exist for this dimension, the default member will be the first dimension member
displayed in the dimension members list.
This modification is not described in the BusinessObjects Extended Analytics Designer user
guide.
2.1.2 Analyzer
• Reviewed Analyzer menus and toolbars
Menus and toolbars have been reviewed and enhanced to make them more user-friendly,
whether you use Excel XP, 2003 or 2007.
• Leveraging Excel 2007 capabilities
Analyzer Excel 2007 version offers new contextual descriptions of the different Analyzer
functions. Moreover, dynamic formatting by report and expand options are directly available in
the Analyzer ribbon.
8
BusinessObjects Extended Analytics 4.1 Release Notes
• Several reports in one sheet in dynamic mode
In dynamic mode, you can now create several reports - connected to one or different cubes - in
a single Analyzer sheet.
• Moving and positionning reports
Several functions have been added in the Report Manager to define the position of reports.
Directional arrows allow positionning the entire Analyzer report in the Excel sheet, while Shift
buttons position row and column headers in relation to the data grid of the report. Moreover,
each dimension in the page header can be positioned individually.
• Sharing report headers
When using several reports of the same Analyzer sheet and using the same connection, it is
now possible to share one or several report headers between them. In this case, any action
performed on the shared header (for example, expand, collapse…) will apply to each of the
reports using this header.
• Hide empty columns available
The Hide empty columns function is now available in the Sheet Options dialog box.
• Filtering based on SSAS attributes
You can now perform multi-criteria filtering on dimension members based on SSAS attributes
deployed in the cube.
• Dynamic formatting by report
When a sheet contains several reports, each report can now have its own dynamic formatting
template.
• Highlighting reports
When a sheet contains several reports, you can use the Highlight function. This function
enables you to differentiate reports from one another. The different parts of the report are
highlighted using colors: page header, row header, column header and data.
• Dynamic asymmetric reports
With the Keep/Eliminate on Single Member funtion, you can now create asymmetric reports
in dynamic mode.
• Deleting reports
Consequent to the multi-reports function, you can now delete one or more reports from a sheet.
The first report created in a sheet can never be deleted.
• Reports persistency improvement
In previous versions, when dimension member names changed in the cube, the dimension
members were no longer retrieved in Analyzer.
Now, if the cube is re-deployed with different member descriptions, Analyzer dynamic reports
will continue to work due to an automatic mapping based on new dimension member internal
identifiers.
As far as dimensions are concerned, you must however manually map each former dimension
with a new dimension name using a dedicated dialog box. The re-deployment of the cube must
be performed with Designer 4.X to use this function.
• Supporting multi member descriptions
Multiple member descriptions are now supported in Analyzer dynamic mode.
You can now choose the caption, or any property defined for the dimension, such as code,
short description or long description.
• Inserting Excel blank rows and columns in dynamic mode
In dynamic reports, you can insert a blank row or column to add a formula, a text or to use as a
separation.
• Connecting and disconnecting several sheets at the same time
It is now possible to connect and disconnect several Analyzer sheets at the same time.
• Refreshing all the reports of a book at the same time
The Read data function has been renamed in Refresh.
|
9
BusinessObjects Extended Analytics 4.1 Release Notes
|
What’s new in this version?
The Refresh function is divided into two functions enabling you to:
Refresh the selected report.
Refresh all reports in all sheets of the current book in one action.
• New custom member editor
A new custom member editor with .net user interface enables you to manage custom members
of several sheets and connections at the same time.
• Exporting and importing custom members
Analyzer custom members can now be exported and stored in .xml files. Export and import can
be performed for several Analyzer sheets and connections at the same time.
2.1.3 Reporter
• New Configuration Manager, Data sources page deleted
Since data sources are now managed in the new Configuration Manager, the Data sources
page has been removed from the BusinessObjects Extended Analytics Reporter user interface.
• Batch print function available for any RDL report
The batch print function is now available in the Printing tab of any RDL report. This function
enables you to generate a .pdf file when printing a report for each of several values of the
dimensions to be set.
2.1.4 New in the documentation
A list differentiates the functions that are specific to the Dynamic Mode and to the Free Mode in
Analyzer.
2.2 New technical features
2.2.1 New server component: Configuration Manager
This new server component is a web site that helps you to deploy, configure and test your
Analytics platform.
To simplify the firewall settings, the SSRS/SSAS Reporter link can be set to use the datapump.
2.2.2 Architecture
It is now recommended that you install the Configuration Manager, Deployer and data pump
components on the SSAS server. However, previous architectures are still supported.
2.2.3 Platform evolution
• All server components (except BusinessObjets Extended Analytics Web server) now
support Windows 2003 64 bits.
• Oracle BusinessObjets Finance database and Oracle star schema databases can
now be hosted on different Oracle instances.
• The administrator client no longer relies on the BusinessObjets Finance client.
• Cartesis Magnitude V9 is no longer supported.
• Only Cartesis Finance 10 SP2 and BusinessObjets Finance 10.5 are supported.
• Microsoft Excel 2000 is no longer supported
10
BusinessObjects Extended Analytics 4.1 Release Notes
3 Migration, best practices &
implementation
Note – The installation guide describes the technical upgrade process.
3.1 Solution migration
The migration process from version 3.5 SP1 to version 4 is explained in the Installation guide.
Important - We highly recommend that you read the Installation guide.
3.2 Calculated members, MDX formulas
When you want to create calculated members and any complex MDX formula (including ‘if’
conditions), you should verify that you can define them in BusinessObjets Finance.
This recommendation is for performance reasons: formulas are stored in BusinessObjets
Finance, whereas they are recalculated in BusinessObjets Extended Analytics.
|
3.3 Single measure
• If you are a new BusinessObjets Extended Analytics client:
Even though the multi-measure is the default mode, we recommend that you activate the single
measure mode right from the beginning.
This will facilitate the handling of reports. .
• If you are already using a previous version of BusinessObjets Extended Analytics:
Single measure mode will simplify the use of reports but you will probably have to modify your
existing reports.
3.4 Internal identifiers for Finance dimension
members
Internal identifiers have been added to the cube in order to improve the stability of Analyzer
reports. Internal identifiers will only work with Analyzer version 4.1.
3.5 Period dimension type
The Period dimension is treated as an SSAS “time” type dimension while the Data entry period
is treated as a “regular” type dimension.
However, if the Period dimension was excluded in the solution you migrate, the Data entry
period will be treated as a “time” type dimension.
3.6 Hierarchy level relationships
To optimize performance, relationships between levels have been modified in hierarchies. A
hierarchy level is now linked to the level immediately below it in the hierarchy instead of being
linked directly to the leaf level (dimension key attribute). Consequently, only the levels
immediately above the leaf level are automatically treated as dimension member attributes in
client applications. Other levels must be manually added as attributes in Designer to be visible
in client applications.
11
BusinessObjects Extended Analytics 4.1 Release Notes
|
Migration, best practices & implementation
3.7 Migrating reports in Excel 2007
Follow the procedure below if:
You are using dynamic reports.
•
•
You are using free reports containing custom members.
To open Analyzer reports with Microsoft Excel 2007:
1. Install Analyzer version 4.1.
2. Open the Analyzer reports with Excel XP or 2003, connect, refresh and save those
reports.
3. You can the n open the reports with Excel 2007.
12
BusinessObjects Extended Analytics 4.1 Release Notes
4 Technical platform changes
All servers Deployer, Reporter and Configuration Manager (except BusinessObjets Extended
Analytics Web server) now support Windows 2003 64 bits.
5 Language and terminology
changes
• The User Interface is available in English, French, German and Japanese.
• The Online Help and User Guide for BusinessObjets Extended Analytics Designer
are available in English and French.
• The Online Help and User Guide for BusinessObjets Extended Analytics Analyzer
and Reporter is available in English. It will be available in French in the next release.
|
13
BusinessObjects Extended Analytics 4.1 Release Notes
|
Appendix – Corrections
6 Appendix – Corrections
6.1 Designer
• DESIGNER GENERATES ERRORS WHEN LOCAL BROKER SERVICE IS NOT
AVAILABLE.
When the local broker service is not available, Designer generates errors when trying to
open and create new solutions. Now when the service is not available the user will not
be able to use the local source for data sources and will be restricted to remote only.
(BOEA01807)
• FIXED PROBLEMS WITH REMOTE DATA SOURCES
Problems could arise in some circumstances when dealing with remote data sources.
These have been fixed.
(BOEA01399)
• LIVE ACCESS SETTINGS NOT SAVED CORRECTLY
Fixed a problem where a custom list of Data Entry Periods used to define the "Live
Access" settings was not being saved and the deployment was reverting to "For all Data
Entry Periods".
(BOEA02106)
• ORDER LIST OF SOLUTIONS WHEN SELECTING ONE TO BE OPENED
ALPHABETICALLY.
When viewing the list of solutions that can be selected from in the Open solution dialog
the solutions are correctly listed alphabetically.
(BOEA01953)
• SAVE SOLUTION OPTION NOT ENABLED
Fixed multiple problems whereby the "Save Solution" menu option and toolbar button did
not become enabled after changes were made to a solution.
(BOEA01767)
• CALCULATED MEMBER CREATION FAILED ON CATEGORY DIMENSION
In Designer, a calculated member can not be created under the root member of the
Category dimension hierarchy. Nevertheless, a calculated member can be created under
an existing category on the dimension hierarchy.
(BOEA02068)
• DEFAULT MEMBERS ARE SOMETIMES NOT SAVED CORRECTLY
Fixed a problem where Default Members in Default Hierarchies and Named Level
Hierarchies were not deployed or saved correctly in some circumstances.
(BOEA02133)
• FILTERS ON DATA ENTRY PERIOD DIMENSION
The error when selecting a Finance filter on the data entry period dimension has been
fixed and the members are appropriately filtered.
(BOEA02361)
• FIXED A CRASH WHEN FILTERING ELEMENTS
Designer will no longer crash if a filtered dimension uses a filter that no longer exists in
the Finance Data Source.
(BOEA02135)
• FIXED A PROBLEM WITH CATEGORY SCENARIO SELECTION
Under certain circumstances Designer would not save the correct Category Scenario
Account Hierarchy selection. This has now been fixed.
(BOEA02663)
14
BusinessObjects Extended Analytics 4.1 Release Notes
• FIXED PROBLEMS WHEN FILTERING DIMENSIONS
Fixed problems in the filtering of dimensions caused when selecting different dimensions
in the Designer Solution Explorer.
(BOEA02344)
• IN A FRENCH CUBE SOME WORDS REMAIN IN ENGLISH
The names of certain objects in the deployed cube and dimensions are fully translatable
in the Designer UI so that the user can enter the desired translation.
The hierarchy name which contains the 'By' word is fully translatable via the UI so this
word can be translated into the desired language. The total caption 'All' is translatable
for all hierarchies via the UI as are the orphaned level names such as 'No Level
Member'.
(BOEA01873)
• MISSING MEMBERS WHEN SELECTING DEFAULT MEMBER.
It is now possible to select from all dimension members for the default member including
special members that do not originate from BusinessObjets Finance.
(BOEA01197)
• ORACLE SOURCE CAUSES DEPLOYMENT ERROR WITH MERGE NAMES OVER 30
CHARACS
When ORACLE is the source Finance database names of some objects need to be 30
characters or less in length. The code has been changed to enforce this by truncating
these object names where required.
(BOEA01076)
• SOLUTION EXPORT CONFIRMATION MESSAGE
When solutions are exported a message will now be displayed confirming success or
failure of the operation.
(BOEA02062)
• SPECIAL HIERARCHIES NOT MAINTAINING CHANGED FROM FINANCE.
When selecting the special account and entity hierarchy the dimension members are
automatically filtered based on the hierarchy from Finance. Changes to these
hierarchies are now correctly applied in the Designer when a stored solutio n is opened.
(BOEA02669)
• TRANSLATE A DIMENSIONAL ANALYSIS MEASURE LEADS TO AN ERROR
The error that occurred while translating analysis measures has been resolved.
(BOEA02096)
• BATCH PROCESS CAN CREATE UNWANTED POPUPS
The issue of using the batch mode deployments and popups appearing requiring user
intervention has been resolved. The problem is now correctly located in the log file and
not displayed via a popup.
(BOEA02070)
• CALCULATED MEMBERS WITH DUPLICATE NAMES
It is no longer possible to create a calculated member with the same name as an existing
calculated member in that dimension.
(BOEA01306)
• DUPLICATE COLUMN ERROR WHEN SELECTING MULTIPLE HIERARCHIES.
The duplicate column error generated when selecting multiple named level hierarchies
and characteristics are shared across hierarchies has been fixed. The deployment
succeeds and the hierarchies are correctly generated.
(BOEA02441)
|
15
BusinessObjects Extended Analytics 4.1 Release Notes
|
Appendix – Corrections
• ENSURE ANY PROPOSED CUSTOM NAMES ARE NOT EMPTY PRIOR TO
DEPLOYMENT.
Checks are now made to ensure if a custom name for a dimension is selected one must
be provided for each language deployed. If a problem is found an issue to resolve is
raised and must be resolved before deployment is allowed.
(BOEA01792)
• ENSURE LAST PROCESSED TIME IS UPDATED WHEN VIEWING DEPLOYMENT
GENERAL TAB.
The last deployed and processed time are now correctly maintained. These values
come from the cube itself and will reflect the correct times.
(BOEA01782)
• ERROR CAUSED BY INCLUDING CLIENT DIMENSION BASED ON PERIODS.
The deployment error displayed when a client dimension is based on periods and
included in a deployment has been fixed. The deployment completes and the dimension
is correctly generated.
(BOEA02076)
• ERROR CAUSED BY SELECTING SIMILAR HIERARCHY ACROSS DIMENSIONS.
The error generated when selecting similar hierarchies across different dimensions
based on the same reference table (e.g. Partner and Rep Unit) has been resolved. In
the case where the dimension name is hidden the hierarchies must have different
names.
(BOEA02042)
• FIXED A CRASH WHEN DEPLOYING DIMENSIONS WITH "CUSTOM FORMAT"
SELECTED
Dimensions with a deployment naming option of "Custom Format" and with a selected
Category Scenario Account Hierarchy should no longer crash when deployed.
(BOEA01959)
• FIXED A PROBLEM WITH "LIVE ACCESS" OPTIONS
Under some circumstances the options for "Live Access" were not saved correctly. This
has been resolved.
(BOEA01193)
• FIXED A WARNING MESSGE
The warning message displayed when deleting an SSAS cube via Designer should now
be correct.
(BOEA01481)
• INCORRECT MEMBERS IN CONSOLIDATION MERGE ON HISTORIZED VIEW.
When using a historized view it is possible that additional members will appear in the
Consolidation merged dimension. Additional fact data will not appear in the cube itself
but it is possible to select members that were not picked from the UI and will therefore
result in no data being displayed in the cube.
(BOEA01881)
• LOGICAL DIMENSION MEMBER FILTER INCORRECT
When filtering members of a logical dimension with only those where data exists, it is
possible that the actual deployed members do not match those selected in the UI. This
has been fixed so that only the required members are in the dimension.
(BOEA02047)
• PERSISTENCY OF PROACTIVE CACHE SETTINGS PER PERIOD
The problem of persistency related to selecting data entry periods as the basis for
proactive cache for the cube has been fixed, the selections are now correctly maintained.
(BOEA02476)
16
BusinessObjects Extended Analytics 4.1 Release Notes
• STAR SCHEMA DEPLOYMENT FAILS IF MANY CHARACTERISTICS IN DIMENSION
DEPLOYED.
When a great number of characteristics are deployed for a dimension, their commadelimited names can be a long string that exceeds the column width limit in the table that
stores the deployment details.
(BOEA02179)
• STAR SCHEMA DEPLOYMENT FAILS IF ORACLE USER IN UPPERCASE.
If a user enters the User Name field without using uppercase letters while setting up an
Oracle star schema connection, the star schema deployment fails with an Oracle error.
Using all uppercase letters for User Name makes the same star schema deployment
succeed.
(BOEA02197)
6.2 Deployer
• DEPLOYEMENT FAILS IF FILTERS ARE USED TO SELECT DIMENSION ELEMENTS.
If filters were used to select elements for one or more dimensions in a view, any
deployments of this view would fail.
(BOEA01732)
• DEPLOYMENT ERROR WHEN SELECTING TWO HIERARCHIES WITH SIMILAR
LEVEL CHARACS.
The error displayed when selecting two different named level hierarchies where one level
from each hierarchy is based on the same reference table has been fixed. The
deployment succeeds and the hierarchies are correctly generated.
(BOEA02030)
• NO DATA IN CUBE WHERE SCOPE HIERARCHY USED AND NO ROLLUP RULE
EXISTS
The named queries for the cube's partitions were not taking into account consolidations
where no rollup rule existed. This has been modified so that now the cube is correctly
populated with all data.
(BOEA02645)
• PROBLEM WITH DEPLOYING ELIMINATION DIMENSION AND DE-SELECTING
MEMBERS.
It is now possible to deploy the elimination dimension after de-selecting members. Some
members rely on calculations based on the other members so it is important to
understand the impact that removing a member from the elimination dimension can
have.
(BOEA02434)
|
6.3 Reporter
• ERROR WHILE OPENING AN XLS REPORT WHOSE NAME CONTAINS SPECIAL
CHARACTERS
For a given session of Reporter, an error occurs the firs time the user opens an XLS
report whose title contains special characters like 'é'. The next times the user opens such
an XLS Report, no error occurs.
(BOEA02477)
• SOME PARAMETER VALUES ARE MISSING WHEN RUNNING A REPORT
In Designer, it is possible to use the option "Hide Dimension Name" when building a
cube. In this case, if a RDL report that contains some parameters is published using
such a cube, some values may be missing at execution time when selecting a new value
for a parameter, depending on the depth of the values hierarchy.
(BOEA02879)
17
BusinessObjects Extended Analytics 4.1 Release Notes
|
Appendix – Corrections
6.4 Security
• ACCESS DENIED TO NEWLY CREATED CATEGORIES
If a user has a default access to categories but some categories are created after the
last modification of the user's data access group, those categories will not be accessible
in Analytics.
(BOEA02700)
• ANALYTICS SECURITY EXTENSION INITIALIZATION DEPENDS ON FINANCE WEB
SERVICES
During its initialization, the Analytics Security Extension for Reporting Services performs
a dynamic discovery of the Finance Web services. Therefore, if an error occurs (e.g.
network error), the initialization fails with a poor error reporting.
(BOEA02681)
• SECURITY UDF ACCESSES ITS LOG FILES UNDER THE IDENTITY OF THE FIRST
CLIENT.
The Security UDF runs under client impersonation to support Windows authentication.
As a side effect, it accesses the log files under the identity of the client connecting to
Analysis Services. If the client has insufficient privileges, the UDF will be unable to log.
(BOEA02671)
6.5 Translation
• BAD ENGLISH TRANSLATION
Instead of having "Supress Dimension Member", we have "Suppress Dimension
Member"
(BOEA02101)
• BAD FRENCH TRANSLATION
Instead of having "Supprimer Membre par défaut", we have "Supprimer les membres de
la dimension"
(BOEA 02102)
18
Loading...