I have an MRE report that when I use the GUI to add a drilldown, it doesn't allow me to go to the edaserve environment.

I figured I'd try coding it in myself, but it doesn't work.

here's the code.
TYPE=DATA,
COLUMN=ITEM_DESCRIPTION,
TARGET='_blank',
FOCEXEC=app/lineitemdetail.fex(ORDER_NUM=ORDER_NUM ITEM_DESC=ITEM_DESCRIPTION),
$


Here's the error.
Error occurred.
ERROR: ERROR_MR_FEX_NOT_FOUND Can't create item object based on provided item key app/lineitemdetail.fex.

does this mean it can't find it? It's in my edaserve under a folder called "Drills", but I tried making it app/drills/lineitemdetail.fex and that didn't work either.

Thanks!

Change your drill to look like this:

FOCEXEC=lineitemdetail(ORDER_NUM=ORDER_NUM ITEM_DESC=ITEM_DESCRIPTION IBIAPP_app=Drills),
  

That way the server will know where to find the focexec.

we've changed it to
TYPE=DATA,
COLUMN=ITEM_DESCRIPTION,
TARGET='_blank',
FOCEXEC=lineitemdetail(ORDER_NUM=ORDER_NUM ITEM_DESC=ITEM_DESCRIPTION IBIAPP_app=Drills),
$


now we're getting...
Error occurred.
ERROR: ERROR_MR_FEX_NOT_FOUND Can't create item object based on provided item key lineitemdetail.fex.


?

Try putting in an explicit URL for your drill syntax. Looks like it is trying to go to MRE and you need to force it out of MRe.

I'm not sure what you mean GinnyJakes.
could you provide me an example of how this works with dynamic data?

I'm passing order_num and item_desc to the fex.

by default, devstudio will only create a fexname up to 8 characters long. How are you getting a fex called lineitemdetail.fex? You may want to check the properties of the fex and see what the actual fexname is as opposed to what is displayed in DS.

To add to what Darin said, if this .fex was created in MRE and then deployed/moved, then the actual name may have no relay=tion to what you thin kthe .fex is calle. MRE creates it's own algorithmic name.

Jason is trying to call a focexec outside of the MRE environment. Those names can be longer than 8 characters.

Jason, try this. I did this in the Report Painter. I put the basic URL in the URL box and then added the parms in the parameter box.

This is the generated stylesheet syntax.

TYPE=DATA,
     COLUMN=N1,
     TARGET='_blank',
     URL=//wfprd/ibi_apps/WFServlet?(IBIF_ex='carsaledtl' COUNTRY=N1 CAR=N2 IBIAPP_app='c758760'),$

we are on 7.6.4. only the stuff we created prior to the upgrade is 8 chars or less. I'm not sure if this is a setting we found and allowed or what exactly.

GinnyJakes: It's working using your example.

Thank you for your help!

jason, would you answer a question for me...
is your host fex in the same mre domain as the drilldown fex?
or, as ginny says , is your drilldown fex somewhere else entirely..

Ginny, what is 'c768760' in your code. Is that an mRE domain directory? or a dir under ibi\apps\ ?

[btw, i'mm in mre764 and i have fexnames longer than 8 chars all over the place.}

Susannah,

It is a directory under ibi/apps. We use our userids to name our development directories.

Jason,

You have to remember how the two distinct environments are structured.

Within MRE all the fexes are held in individual folders under (i.e. 7.6) [drive:/][install directory]/ibi/apps/webfocus76/basedir. Each sub folder relates to a user or a domain within MRE and the domain folders will generally have three subfolders themselves. App, Import and MRV. App is where the MRE fexes live, Import is used for (yes, you guessed it) importing files (fexes, .mas, .acx etc.). The basedir folder resides on the Client Server install which can be a completely different machine to the Reporting server.

For your Apps folders (don't confuse these with the above), you have to look to the Reporting Server under the ibi/apps directory. There will be folders under apps that relate to folder names that you might include in your APP PATH. The folders that you see within DS under Data Servers, are virtual and only exist as a filter list, not a physical folder.

When you are in MRE, any drilldown that you code would normally have app/ prefix, and this can be a good method of identifying it as such. So for your first error, you needed to have a fex in the same (generally) "app" folder.

If you want to specify a fex within one of your RS "app" folders, then you need syntax such as that Ginny gave you. However, you have to understand how you are referencing the RS "app" folder and file. This is where Ginny's mention of the IBIAPP_app value of "drills". IBIAPP_app identifys the "app" folder on your Reporting Server where your drilldown fex exists. When you copied Ginny's code, you probably just copied it and hoped it would work, but it would only work if you had the app folder called "drills".

So, your second attempt to drilldown really needed this -

TYPE=DATA,
COLUMN=ITEM_DESCRIPTION,
TARGET='_blank',
FOCEXEC=lineitemdetail(ORDER_NUM=ORDER_NUM ITEM_DESC=ITEM_DESCRIPTION IBIAPP_app=[app folder on your reporting server where lineitemdetail.fex exists]),
$

Hope that helps?

T

aha! ginny, what a good idea!

Unfortunately, as per hammo1j's posting Is there an Easy way to Drilldown to Application .fex from MRE launched fex? Developer Studio does not allow you to link to a self service fex from an MRE drilldown. It appears the only way to do that is to use the URL method that Ginny suggested or to call a JavaScript function.

Please see here for a potential solution:
Is there an Easy way to Drilldown to Application .fex from MRE launched fex?

Jason

I think I have something reasonably practical now.

You code a stub on MRE to launch the application and then switch context to the application using EXEC.

See the above link.