Is there any way for me to build a report with parameters and then
schedule it to go to different people with different parameters through
Crystal Enterprise? For example, I have a report and the parameter is
client name. I want to schedule it so that on the first of the month,
it’s run for client A and sent to client A, but also have it run for
client B and be sent to client B. Any help would be great! Thanks!!
I have somethign similar; where the same recipient needs three versions of the report delievered at the same time each week. The reports differ only in the one parameter passed to the report.
I can only set one default param and the schedule wont seem to allow variations on param default based on schedule instance.
Any better work-around than triplicating the report on the server. I really want to reduce the clutter.
How do I set it to another value when scheduling? The only place I can see that I can set the param value is on the Process-Parameters tab of the Central Management Console.
So if I set that (the param default), create a schedule (call it S1); change the param default and then make another schedule (lets call that S2); both S1 and S2 run with the last set param default.
I really hope im just missing somethign simple here.
In InfoView; I browse to the report; click SCHEDULE; pick hourly; Then jump down to Parameters; then click on the one I want to change.
It opens the new dynamic list, I pick the value I want.
Then click OK.
and I get:
Server Error in ‘/businessobjects/Enterprise115/InfoView’ Application.
Exception from HRESULT: 0x8004100D.
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.
Exception Details: System.Runtime.InteropServices.COMException: Exception from HRESULT: 0x8004100D.
Source Error:
An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.
Is the field you’re applying the prompt to in a hierarchy and not the top level? I’ve experienced weird prompt errors when I tried to apply a prompt to a lower level of a hiearchy…