We have a number of Crystal Reports 2011 reports that are currently automatically executed and exported by a custom .Net Winforms scheduling application. These reports all use SQL Commands with hand-crafted SQL to get the best performance against a third party schema that we cannot modify.
A number of the reports include date parameters that are usually set to something like the previous business day, or start of last month etc, and the values to be applied to these parameters when the reports are executed are calculated by the scheduling application against the current date. These parameters are SQL level parameters, in order to reduce the result set coming back from the DB.
We now have to migrate the Crystal Reports reporting onto Business Objects. In order to maintain the performance of the report SQL, we want to re-use the Freehand SQL from the Crystal Reports in Web Intelligence reports, or in Derived Tables in a minimal Universe - we don't want to create a Universe against the target schema.
We need to be able to automatically schedule the Webi reports on a daily basis, and have the date-based parameters calculated and passed in, with the results exported in Excel and PDF format, as they are today (the users will not be getting access via a web interface - they will just pick up the exports from a network drive). We ideally want to keep parameters so that reports could be run adhoc for different date ranges.
What I want to know is, how should this parameterisation and automatic default value calculation best be supported in the BI technology? I cannot seem to get default values working with the @Prompt() function, and when the reports are refreshed daily, there won't be a user there to respond to a prompt anyway. What would be the best approach here?