Categories
- All Categories
- 15 Oracle Analytics Sharing Center
- 14 Oracle Analytics Lounge
- 211 Oracle Analytics News
- 41 Oracle Analytics Videos
- 15.7K Oracle Analytics Forums
- 6.1K Oracle Analytics Idea Labs
- Oracle Analytics User Groups
- 77 Oracle Analytics Trainings
- 14 Oracle Analytics Data Visualizations Challenge
- Find Partners
- For Partners
Column Filter Condition...
Hi All,
I have a subject area built where the FILTER(measure_column USING (condition)) function does not appear to working at all. For example FILTER(facts.num_purchased USING (Region.state = 'NY')) does not appear to filtering by New York.
All other the subject areas in my environment that use this function are fine.
Any quick thoughts on why this is?
Thanks
Answers
-
Your problem description is quite vague. What do you mean "does not appear to filtering by New York" - did you verify this in detail? And if so - what do the query logs say in detail? Did you check the logs and the physical query emitted against the source database?
0 -
Hello,
Thank you for responding
What I mean is, just running number purchased, just the fact measure, without any filter in the column or the report, returns 10,000, for all time periods and locations. Adding NY to the report filter, pairs it down to 500. Trying that filter directly in the column itself using the filter condition Filter(measure_column (using(condition)) does not work, it still returns 10,000 where I would expect 500.
The SQL being issued in the query logs are submitting the correct syntax. Its very very strange, I was wondering if I missed a setting somewhere or accidentally switched something off.
0 -
Hi,
are you saying that the physical SQL send the filter but you get 10'000 back even if the query does return to your BI server 500 ?
That's sounds like ... impossible to me ...
0 -
I agree it sounds impossible, that's why I'm here, wondering if I'm missing something very simple.
0 -
Keep look into this, I believe something is wrong in your report !!
0 -
Check your syntax ... if need be simplify your report to the bare minimum and get the filter correct first ...
If that doesn't work, then time to check the SQL sent to the Database (one where it works with report filter; one where is is not working with column formula filter) ... post those SQLs.
0 -
Thank you all for the responses. Going to tackle this issue again next week. Will let you know if I figure it out.
0 -
Hi All, just wanted to respond. The physical sql DOES NOT look like its picking up the column condition at all. Which is strange because in the Logical SQL its there, but when comparing two physical SQL statements (one that works and this one that doesn't).
Can I try to force it in the XML or SQL and see what happens or does anyone have a thought?
Thanks.
0 -
does the physical SQL have the filter condition in the where clause or does it have the filter column included in the selected columns / group by clause?
Post the SQL
0 -
Hi Thomas, thanks for responding.
It doesn't have the filter condition at all. The syntax appears as if the column is completely vanilla. The syntax is appearing as a simple SELECT Count FROM Fact Table.
Just for reference, I'd tried rebuilding the RPD, same problem, and I tried this on a different version and same problem.
0
