I worked years ago as an EUL administrator with the Oracle Discoverer tools. We found a problem that troubled us during days: Grand Totals for some columns were empty despite of containing data that should be shown. The info was visible only when there was only one record to be added up but only an empty cell was displayed when there were more than one.
That seemed to us like a glitch or bug in this tool but it came out to be a technical decision of the tool’s designers. Let me explain:
Let’s see an example. If we got a master folder with data from official tourist guides, which includes their fares, like this:
There is a few workarounds to fix this:
- Maybe the amount being added should not be at the Detail folder. Should the database design be reviewed?
- Check if the relation between master and detail folder is 1 to 1 but it is mistakenly set as 1 to many.
- If everything above is right, there is one more thing that you can do: Tell Discoverer that it should add up those amounts anyway. To do so, follow these steps:
- Activate the ‘Show the sum of the values displayed in the contributing cells‘ option at the Discoverer Desktop settings.
- Set the properties AllowAggregationOverRepeatedValues and AggregationBehavior to 1 instead of 0 at the prefs.txt file that you can find in Discoverer server path $ORACLE_HOMEDiscovererutil.
This latter case should be taken being aware of what that implies. Even if it were a perfectly valid solution for the case you are trying to fix, it could exist another report, now or in future, run at the same patched server, which wouldn’t allow the administrator to see there is a problem (fan trap) and totals or summary fields are displaying wrong amounts as they are being added up two or more times (like the Juan’s fares).