Impromtu Reports questions/help? 1

[wolves]

When I do a drill-through from the PowerPlay cube, it opens up Impromptu, which I assume sends the query to the database I am connected to.

Scenario:
I have a dimension named 'Pay Year', and a measure named 'Total Charges'

When I for instance choose 1983 for my 'Pay Year', and 'Total Charges', and drill through, it opens up the Impromptu which sends the query to the database.

Now, since the table this queries have a few million entries, the query that it sends to the database is basically selecting ALL from the table, then I assume that Impromptu will filter and only show me what I want to see on the report, in this case just 1983 data.

I would have though that Impromptu would send a query to the database similiar to 'Select * from table where PAY_YEAR like '1983%', and just bring that data.

Is there anyway to 'trick' the query sent from Impromptu, so that it does not have to retrieve millions of data first, just the data that I need during a drill-through?

Or am I missing the whole concept to the drill-through process entirely?

Thanks in advance,
J

 

[drlex]

wolves,
From your description of events, it sounds as though the drill-through (or "drill-thru") has not been properly configured; what you anticipated sounds to be appropriate. You'll need to check with the transformer model that gave rise to the cube. It may be that there is some cogent reason why the levels and/or queries cannot be passed in the query made to the database.


soi la, soi carré

 

[DoubleD]

wolves,
Is Pay Year a date dimension in the Model?
Is Pay Year a date field in the database?

If the answer to these to questions don't match, you'll need to add a calculated field in your drill-through report to allow Impromptu to pass the correct query to the database.

I am what I am based on the decisions I have made.

DoubleD

 

[wolves]

Great point DoubleD.
Being new at it, I did not put that together. Let me check that out now and see what happens.

Thanks again.

 

[wolves]

Thanks DoubleD.

I did end up adding a calculated field in to allow Impromptu to pass the correct query to the database.