Need dataset to prompt for date during refresh

[tushar gaurav]

Hi Cognos Experts,

I have a data module which is created from a sql statement.
I have created a dataset from it and now I need the dataset should prompt for dates upon being refreshed.
I have created parameter filters for dates in the dataset query and then I saved it.
The dataset prompted for dates while saving ,which I have provided.
It seems the dataset saved these dates in cache as whenever I have tried to refresh it,it gets refreshed without asking for dates.
I have cleared the parameter values before refreshing, it but I didn't get the prompts for date.
Is there anyway I can get the prompts for dates while refreshing the dataset.
*I am using COgnos Analytics 11.2.4

Thanks and Regards,
Tushar Gaurav

[dougp]

Datasets seem primarily for collecting reduced or summarized sets of data from sources to improve report performance and to encapsulate a minimal set of elements for ease of use.  Most often, they should be refreshed automatically on a schedule or a data event.  When a dataset is being refreshed automatically (without user interaction), how would Cognos present a prompt page?

You should design your dataset to get the data needed for all dependent reports.  The prompting should be in the reports.

If the dataset should be refreshed based on a date, consider computing the date rather than prompting for it.

[tushar gaurav]

Hi Doug,

Thanks a lot for your response.
Actually I have provided a date filter in the sql used to create the data set to have last 30 days of data.
However it may possible that there wont be data in database for last 30 days, so in such scenarios I wanted to have prompts while refreshing the dataset and was checking its feasibilty.
So can you please let me know if providing prompts while refreshing the dataset is feasible?

Thanks and Regards,
Tushar Gaurav

[dougp]

prompting should be in the reports.

[bus_pass_man]

No, you can't build prompt filters or filters of any kind into a data set.  A data set is a table.  It stores the data which was available to the person who created it.  As a side note, this means that a data set can expose data which otherwise is secured and forbidden to some users.

You have this weird structure and I'm not sure why. What are you trying to do? 

You have a data module created from a sql statement.  Why? Just one table in the data module?  It is possible you mean something else?  What is the ultimate data source for your application?

You don't mention what you want to do.  You are defining the problem in terms of how to implement this particular technical approach rather than the business objective, which might be better achievable by something more elegant than your Rube Goldberg set up.

Presumably you want to pre-aggregate stuff in some way, which would explain why you created the data set. 

You would be better off if you created what you want in a view in your data base, and use that.  The maintenance overhead would probably be lower too.

You could then place the filters in a location where they would be available in the manner you want.

If you need them to be available everywhere you could create stand alone filters in the data module. 

If you need them to be executed every time, you could embed them in the query subject.

You could create them in your report, but that would mean that you would need to create them in any other relevant report as well, which would be tedious without considering the maintenance headaches.