Searching a slicer in my Direct Query report blows it up (ORA-00904)

[oktober42]

Good afternoon! @Anonymous and I are building a report that performs a Direct Query to an Oracle database with a custom SQL query (that we feel is optimized) through a gateway. We originally had several search boxes with the Text Filter visual added, but when we would search we would immediately lose all the visuals. We replaced this with a slicer. It takes a moment for all the values to load, but when we select one it works. If we attempt to search the slicer at all, we lose the slicer visual with an ORA-00904 (invalid identifier) error. 

If the slicer has loaded all the selections, is it passing the search through SQL? I assumed it would just search in local memory. Do we need to do something funky to the SQL query? Is this just an optimization issue? Hopefully we're not the only people fighting this. Thanks in advance!

[lbendlin]

Direct Query = EVERYTHING is passed back to the source.  What's the cardinality on your slicer column?  Do you have an index on that column in the database?