I have a report which requires the user to enter a date range.
I would like to take the yr and the month from the date entered and include them as a column in the report and I would like those values to be exported.
Is there some way to do this?
Tia
Darlene
Thanks Dhirendra
That works to a point in that we can get the columns to show on the report.
However, when we try to export the results to an rdbms, the new fields don’t show.
Any idea how to get them there?
We’re trying to dump this into an access database. Not really sure why at this point.
Thanks
D
Report level variables (like UserResponse) are not going to be included in the data provider export (by definition). Your alternative is to create a simple report that displays every row and column from the data provider. You can then add the report variables to that same report. The bad news now is that exporting report tabs is limited to tab-delimited text files. You can’t export directly to the RDBMS, but MS Access can easily link to / import from the tab-delimited text file. Take a look at the white paper attached to this topic for more details / options.
Or better yet, create actual Designer objects for the @variable or @prompt syntax. Then simply include them in the query panel as a result object.
I create a separate class in my universe that holds one object for each prompt. The object contains only the @prompt syntax. Any place else that the prompt is needed, I reference the one object with the @select syntax. That way if I ever need to change the prompt (the text, the LOV, etc.), I only change it in one place. The side benefit is that I have an actual object that can be used to return the prompt choice as part of the data provider if needed.
If Darlene is using query panel based prompts (not in Designer) then the “Do not regenerate SQL” approach is another option for getting the prompt into the data provider. Generally, “Do not regenerate SQL” is to be avoided for production use (can be a maintenance nightmare), but it is an option.