I have scheduled a chained report in Report Caster as like any other report to run on specified intervals. Looks like there is a known problem with Reports Caster to run a report that is chained with another. If this is true, does anyone has a solution for this issue?

Much Appreciated!

This message has been edited. Last edited by: Kerry,

Are you talking about chained parameters or reports with drilldowns in them? What is the output format? Have you looked up FOCEXURL? If the problem is the latter, that might fix your problem.

If the problem is not either of those two, please describe in more detail.

The report is with the chained parameters and not with drill downs. The output format is HTML.

Hi Rakesh,

Has this issue been resolved?

I passed this one to our internal technicals and was suggested that you may want to open a case with Customer Support Services for assistance. The phone number is 1-800-736-6130, or access online at InfoResponse.

Cheers,

Kerry

Hey Kerry,

Thank you for following up on this. This has been resolved.

Rakesh.

Anything that is run through ReportCaster needs to have the parameters values set either through -DEFAULT, -SET, or as inpout values from the parameter values under Advanced option in RC. So I'm not sure what chained parameters has to do with a RC problem. to RC, a parameter is a parameter - chained or not - and needs to be resolved before it will run.

Having said that, you mention having to "run a report that is chained with another." Not quite sure what you mean by that. Are you just wanting to run multiple reports together? If so, have you tried the a compound/coordintated report? Report Caster can only distribute a single output per task, so you can add multiple tasks, or create all reports using the compound reporting features and then distribute. Maybe you can clarify exactly what it is you are trying to accomplish.

But just as I post, I see your response that it is resolved. Maybe you can follow up with a clarification of the issue and how you resolved it so others can benefit in the future. Thanks.

Looks like it was just my single sign on login permissions problem, which ran the report successfully when fixed. My original report was fine and did not had any problems. Thank you guys for all your help and valuable suggessions.

Rakesh.