<p>I want to provide ad-hoc reporting (not dashboarding or pre-designed reports) to our users in iHub 3.0 (yes, old version--upgrade planned next year) on a star schema design (one fact in the middle, several dimensions equi-joined). </p>
<p> </p>
<p>I'm thinking it's an education issue.

When I create a new report based off my Data Objects data model, my "filter" button (funnel in upper left) is disabled. I do have the ability filter at report creation--"pick your fields, measures, filters" pop-up window, but not afterwards. </p>
<p> </p>
<p>One way I can get that same filter button enabled and usable is to choose a new report based on one of the data sets that constitute the underlying data model (I'm planning on hiding these from the user in the end).</p>
<p> </p>
<p>Here's what I've done to get here:</p>
<p>* created/configured Data Source using a "Query Builder JDBC" Oracle 11g Type (Actuate JDBC didn't allow for SQL "pushdown").</p>
<p>* created a Data Set for my fact (select * from schema_owner.purchase_order)</p>
<p>* created a Data Set for one dimension (select * from schema_owner.po_status)</p>
<p>* created a Data Model and joined the two data sets on the key field, ensuring that the option to automatically disable pushdown is NOT checked. (I don't want to materialize/cache the data, needs to hit Database)</p>
<p>* published the .datadesign to iHub and created new Report selecting the .datadesign file</p>
<p>* choose the Data model object (and only the Data model object) to use as a data source for the report.</p>
<p> </p>
<p>I'm new to Data Objects, but am familiar with Info Objects. It surprises me that there is no table mapping in Data Objects that I can find--the best I can do is make a data set that is scoped to a single table (select * from table). My desire is to have actuate write a single prunable select statement, the equivalent of optional-joins under info-objects. Am I on the right track?</p>
<p> </p>
<p>Thanks in advance for any help! </p>
<p> </p>
<p>John</p>
<p> </p>
<p> </p>
<p> </p>
<p> </p>
<p> </p>