Categories
- All Categories
- 15 Oracle Analytics Sharing Center
- 14 Oracle Analytics Lounge
- 212 Oracle Analytics News
- 42 Oracle Analytics Videos
- 15.7K Oracle Analytics Forums
- 6.1K Oracle Analytics Idea Labs
- Oracle Analytics User Groups
- 78 Oracle Analytics Trainings
- 14 Oracle Analytics Data Visualizations Challenge
- Find Partners
- For Partners
Optimize to fold the case expression on the argument to have same effect as direct SA column

As what Oracle Support suggested, this would have to go by an Enhancement Request to Oracle FAW Idea Lab
SR 3-33605888811 : Column Selector Using Parameters in Oracle Analytics doesn't Aggregate Numbers Correct
Dev team went through the test case which I created internally to reproduce your issue. Dev team responded as follows -
======================================
The problem is the grain of the query is altered with that case statement.
The non working case (report with the calculated column based on the parameters) is pulling every when clause from the case for aggregation.
The working case (report with the direct column) is pulling only 1 direct subject area column.
Unfortunately, there is no solution here.
we don't have the ability to reduce the case statement today.
======================================
Since this is new feature introduced in OAC and it never worked in the past. This is not considered as a regression to code or not considered as a bug.
As an enhancement request to the code - The feature can be implemented as an optimization to fold the case expression on the argument supplied which will have same effect as the direct subject area column
We request you to raise an idea lab request from your side following this document - How To Create An Enhancement Request In Idea Lab For Oracle Analytics ( Doc ID 2662737.1 )
We can conclude this SR as an enhancement request to Oracle Analytics - DV product.
Hope it is clear.
Thanks & regards,
-Rajesh P.
Comments
-
Thanks for the idea.
We previously reported a similar problem to Oracle, and they acknowledged it as a known issue, directing us to this discussion thread.
I'm somewhat surprised that it hasn't been classified as a bug but rather as an enhancement request. This is because the parameter functions correctly in other Subject Areas, except for the one we reported, resulting in inconsistent behavior.
If this parameter (x) doesn't function as expected, it significantly impairs its utility for us until it gets fix.
Rgds,
LipLooi
0