Hey guys,

I am hoping that someone a little bit more experienced and knowledgeable in Reportcaster can point me in the right direction.

I have a lot of schedules in Reportcaster that execute procedures that need a "Year" parameter to run. Now, from looking at a lot of previous threads on this, I have come to the assumption that if I ran a pre-processing procedure in my schedule, that pre-processing procedure could "feed" my schedule/procedure a value to put in the parameter. I might be totally off base here, so feel free to correct me if I'm gathering the wrong conclusions.

So I have a primary procedure (PreProcTest2.fex) that needs a "Year" parameter, and I've written a Pre-processing procedure (PreProcTest.fex) that saves a table and then READs from that table to produce a variable "&YEAR".

The goal is to have "&YEAR" be used as the parameter value for my primary procedure that I'm scheduling. Is this the right way to accomplish my goal? If so, when setting up the Task Parameters, do I just put the literal string "&YEAR" (without quotes) as the value for the "Year" parameter?

Also, how do I properly reference my Pre-Processing procedure in the Pre/Post-Procedures section? Right now I'm using something that looks like: "/WFC/Repository/institut/std_reports/user8/Test/PreprocTest.fex" but I keep getting a Task error: THE FOCEXEC PROCEDURE CANNOT BE FOUND: so I've got to be referencing it wrong there.

Thank you guys for any and all help you can give me!

This message has been edited. Last edited by: FP Mod Chuck,

I've tried to use the pre-processing procedure in the past, but never had much luck.

Now I just schedule out a fex that includes multiple fex's.

For example:

ReportCaster schedules sch_report.fex

sch_report.fex:
-DEFAULT &YEAR = '2017';

-INCLUDE PreProcTest.fex
-INCLUDE PreProcTest2.fex

Does

quote:

"/WFC/Repository/institut/std_reports/user8/Test/PreprocTest.fex

is Published ?

Have you referenced using RC GUI ?

My limited experience would suggest the following:

+ First, move your pre-processing procedure to the Applications area. Your path should look something like "application_name/my_proc.fex". In my version of App Studio, there's a button on the left called "First" that you can use to browse. You might not realize that it's a button, but click it anyway!

+ Second, if you're defining a value for the variable, you don't have to supply a value in Report Caster - just remove it from the parameters list.

I believe this to be correct; please let us know if you find otherwise!

quote:

Originally posted by MartinY:
Does

quote:

"/WFC/Repository/institut/std_reports/user8/Test/PreprocTest.fex

is Published ?

Have you referenced using RC GUI ?

It is published. I'm not sure what referencing in the RC GUI is referring to. When I look at the log, it looks like this:

"Task domain: institut/

Retrieving WebFOCUS Report: IBFS:/WFC/Repository/institut/std_reports/user8/Test/PreprocTest2.fex

Connecting to server EDASERVE with execution id rray9895 at 2017-03-02 16:24:20.799-0600 (1,488,493,460,799)

Connection to the Reporting Server EDASERVE established at 2017-03-02 16:24:20.812-0600 (1,488,493,460,812)

The time to establish a connection to the Reporting Server EDASERVE was 0.013 seconds

Executing pre-rpc: /WFC/Repository/institut/std_reports/user8/Test/PreprocTest.fex

/WFC/Repository/institut/std_reports/user8/Test/PreprocTest.fex

Task error: THE FOCEXEC PROCEDURE CANNOT BE FOUND: "

quote:

Originally posted by Mathematical Rob:

I'm behind the times, and not using App Studio yet (My IT people have been telling me that I will upgrade "Soon" for a while now). There is just text for "First:". I actually tried clicking it to see if it actually was secretly a button, but it wasn't

But based on what you are saying, I am going to try institut/PreprocTest.fex in that field and see what happens!

Nope!

Mathematical Rob (or anyone else that successfully uses a pre-processing procedure) can you post the part of your Log File that references the Pre-Processed report so I can see what syntax or path I'm supposed to be putting into that field?

The pre processing procedure needs to reside on your reporting server (EDASERVE) in one of your app path directories. For example, if your store your pre processing ../ibi/apps/baseapp then you would reference in as baseapp/PreprocTest.fex

Awesome! I got it now!

Okay, so I don't know if the rest of you have issues with how your environment is set up, but here was the problem for us. The way our environment was set up is that all of our procedures exist in the Content Tree.

I had to move my procedure under the Data Server for it to recognize it. For me that is Data Server > EDASERVE > Applications > newapp > Procedures. None of my other procedures exist there, so that is why I didn't think to do it that way.

Once I did this, I was able to call the procedure by typing "newapp/PreprocTest.fex

I still need to figure out how to properly pass the parameters from the Pre Proc to the scheduled task, but I at least solved one issue.