After searching the forum to solve a problem with reportcaster drilldowns, I've run into another problem.

I've added
SET FOCEXURL = HTTP://svr99wfrs/ibi_apps/WFServlet

as the first line of my reportcasted fex that drills into another fex called "open_items" under dev studio properties for the .fex it shows it's location as
app/open_items.fex

now, when I run the report, it comes up fine but the drill down gives me an error of
(FOC227) THE FOCEXEC PROCEDURE CANNOT BE FOUND: app/open_items

everything looks fine in the url,
http://svr99wfrs/ibi_apps/WFServlet?IBIF_ex=app/open_items&CLICKED_ON=&ORDER_NUM=970054717

and when I remove the
SET FOCEXECURL line it works fine with URL of
http://svr99wfrs/ibi_apps/WFServlet?IBIF_webapp=/ibi_ap...sbiuq9/xosbiuq9.htm&IBIF_ex=app/open_items&CLICKED_ON=&ORDER_NUM=970044261
for the drill down.

Where's all the extra stuff coming from that makes it work?
specifically, this...
?IBIF_webapp=/ibi_apps&IBIC_server=EDASERVE&IBIWF_msgviewer=OFF&&IBIMR_drill=X,xosbiuq9/xosbiuq9.htm&

Thanks!

This message has been edited. Last edited by: Jason K.,

ok, I took my fex and put it in the edaserve and took it out of the MRE, and it seems to be working just fine.

So, I'm assuming this has something to do with security? Is there a way to drill into an MRE report from a reportcasted email?

We don't like creating anything but metadata and non-display jobs on the edaserve if we don't have to.

Jason,
Your URL which to you looks ok:

URL=http://svr99wfrs/ibi_apps/WFServlet?IBIF_ex=app/open_items&CLICKED_ON=&ORDER_NUM=970054717

is in fact a url that indeed will not work.
The other one however does.
The additions are what makes it work.

?IBIF_webapp=/ibi_apps&IBIC_server=EDASERVE&IBIWF_msgviewer=OFF&&IBIMR_drill=X,xosbiuq9/xosbiuq9.htm&

IBIF_webapp tells the system where the webapplications can be found (ie webfocus and reportcaster, the war files and directories).
IBIC_server, well that sort of standard, not really needed, but better be safe then sorry.
IBIF_msgviewer is set to off, you don't need that.
The last part is what really matters, since that indicates that this is a MRE drilldown, located in this directory and controlled by this html file. The html location is th elocation of your domain and the domain control file.

In the first URL, the one that looks ok but isn't, you try to run a fex called app/open_items. This would have worked if you would have had a directory called app under your approot. But that's obviously not the case, so that request looks ok, but fails, it can't find the folder app under the approot.
The folder is located in your domain folder under MRE. SO the second URL does work, since it points to MRE.

Does this explanation help a bit?

thanks GamP. After reading your post, I took the 'app/' off and it still failed, so I went ahead and created the fex in the EDAserve environment and the drilldown is working now.

thanks again.

Well, a few months later, we've discovered our solution is too much trouble to maintain, so we need a better answer.

As a quick summary of what happened, when we add a FOCEXURL line to our pre-process in reportcaster, the drilldowns will only allow a drill down to a report in the EDASERVE environment, not the MRE environment. So, our solution was to simply make a copy of the .fex in the edaserve environment and it would work.

How can we drilldown to a report in the MRE environment from a reportcasted email in 7.6?