Posted: Sat May 10, 2008 2:06 am Post subject: Avoid Duplicate Row Aggregation
Hi All, I have another "report configuration" question:
I have a global equity report that returns shares exercised details. This means that for every employee that had exercised shares, we'll report each transaction as detailed rows in the report.
In BO 6.5, this report worked perfectly. The report has 10 columns, 7 of the columns detail information about the share (i.e. grant number, stock ID, grant date, etc.) while the last 3 columns detail $ values. In the event that an employee exercises 3 separate "chunks" of shares within the same time period, all 3 transactions will appear on the "detail" report.
In BO XI, this report is not working correctly. In the example above, the report will unwantingly "merge" those 3 transactions into 1 row, throwing our total row count off (not to mention ruining the integrity of a "detail" report). It seems like in XI, the 3 rows is being treated as duplicates since the first 7 columns are the same for each transaction. I found that by going to Edit Report -> Properties -> Display -> and check Avoid Duplicate Row Aggregation, this solves the issue and it forces the report to display all transactions.
In BO 6.5, this option doesn't have to be checked and the report still works fine. What is the difference on the BO tool that causes it to evaluate this scenario differently in 6.5 vs XI?
Posted: Sat May 10, 2008 2:25 am Post subject: Re: Avoid Duplicate Row Aggregation
I dont have WebI 6.x, but probably the display->avoid duplicate row aggregation option was not available until 6.x and was added in XIr2.
So by design XIr2 WebI has the aggregated rows which can be overridden while in 6.x it used to show duplicate rows.
Its my understanding and I may be wrong.
. _________________ BO 6.x/ BO XIr2/XI 3.1, Oracle 9i/10g//11g, SQL Server, DB2, IIS .Net/Java (Tomcat)
Posted: Sat May 10, 2008 10:03 pm Post subject: Re: Avoid Duplicate Row Aggregation
Actually, I think I may have forgotten to mention but this option was available in both BO 6.5 and XI2. In 6.5, the report works fine if you leave it checked. In XI2, the report only works if you have this unchecked.