Wednesday 25 March 2009

How to Maintain Alignment for Collapsed Items through Sessions ?

Some questions arrived on why if items which are part of an hierarchy are collapsed, they loose the format definition like alignment ?

Well, this is expected behavior. Indeed, every time an item is removed from the layout and added back in a different session it's treated as completely new item and doesn't matter whether it is part of an hierarchy or not. Indeed, this is because the format layout of items is defaulted in the EUL, and in Discoverer Desktop one can maintain control of the format only on the session not on the default properties like alignment.

So, to make alignment persistent on Discoverer Desktop, the default properties for that item should be changed in Discoverer Administrator :

1.) Open the business area on Discoverer Administrator ;
2.) Expand the folder where the item reside ;
3.) Right Click on that item and select Properties ;
4.) On properties dialog box, select the wanted alignment

Monday 9 March 2009

Aggregation: DECODE & CASE calculations returns different values between Discoverer Plus and Discoverer Desktop 10.1.2

(This post does not want to discuss how aggregation works, it assume that you already knows aggregation behavior, but it gives you solution to most known scenarios)

From Discoverer 9.0.2 and above i.e Discoverer 9.0.4 and Discoverer 10.1.2 has enhanced roll-up and calculation capabilities a feature called Enhanced Data Aggregation where when connected to a 9.0.1.4 or higher database, the Discoverer server will rely on the CUBE, ROLLUP and GROUPING SET database functionality to compute roll-up values. This new capability correctly handles many of the restrictions described in the provided note, so that a roll-up value can be computed where the 4i server would have to resort to using the "N.A" string.

Additionally, enhanced Data Aggregation is present only in the Discoverer Middle-tier(Plus and Viewer) server -- Not Discoverer Desktop. You will see aggregations in Plus and Viewer that show up as "N/A" in Desktop.

By the way, we can define:

Linear Calculation
A calculation for which the aggregate value is same as the value obtained by summing up the individual values is a linear calculation.

Locally computable Calculation
Discoverer can locally compute all primitive arithmetic operations (+, -, *, / etc), a subset of aggregates (Sum, Sum_Squares, Count, Max, Min, Average and Variance), some string operators, and Decode. Discoverer can locally compute most calculations that can be broken down into linear parts and that involve the above set of operators.
Calculations such as Sum (Profit) / Count (Profit) can be locally computed as it can be broken down into two Linear Parts Sum (Profit) and Count (Profit) combined by the division operator. Calculations such as Sum (Profit) / Count_Distinct (Profit) cannot be locally computed as one of the parts (Count_distinct (Profit)) is not Linear.

Non-Aggregable Calculation
A pre Oracle 9i database allows data to be fetched at only one level of aggregation. From this data discoverer has to compute values at higher levels of aggregation to support things like totals, outline values etc. This is possible only if the calculation is either Linear or Locally computable.
If a calculation is neither linear nor locally computable it will be marked as non-aggregable. The value specified in the option “Show non aggregable values as “ is displayed for such cells.

Case / Decode
Totals on aggregate calculations involving a case expression might yield non-intuitive results. This is because the item values involved in the condition part of the case expression will become NULL when they are rolled up on that item.



In most of cases the solution is to add in the PC Client where Discoverer Desktop is installed regedit entries, like:

o Add two DWORD values named: AggregationBehavior & AllowAggregationOverRepeatedValues = 1 under the key: HKEY_CURRENT_USER\Software\ORACLE\Discoverer 10\Application\ and set both to 1;

Then, Discoverer Desktop should be closed and re-launched.

Monday 2 March 2009

How To Specify The Owner Of Workbooks On The Viewer Url Parameters ?

On Discoverer Viewer/Plus 9.0.4 it was possible to specify the Owner and Workbook Name on the same url parameter :

wb=.

In 10.1.2 this URL parameter is not getting the Owner anymore, just the workbook name.

This is because, the Discoverer Viewer is not checking whether owner name is prefixed to the workbook.

The fix has introduced a new URL parameter "wbkowner" to specify the Owner's name explicitly.

Hence if the owner needs to be specified then instead of prefixing the owner's name to workbook name the user needs to append new URL parameter "wbkowner=Owner's name".
Since, the "." a is valid character for workbook name, the Discoverer Viewer 10.1.2 wouldn't be able to differentiate whether the string of characters before "." in workbook name is owner's name string or substring of workbookname.

The fix is available on top from 10.1.2.3 + Cumulative Patch 2 onwards, where the parameter "wbkowner" can be used on the URL for Discoverer Viewer.

Discoverer Plus users should wait for internal bug to be fixed.