Hi guys,

I read lots of posts about this on the forum but I still can't do this. I need reference a fex in MRE and I can't find the correct way to do this. On EDASERVE it was very simple:

   
<INPUT TYPE=HIDDEN NAME="IBIF_ex" VALUE="at_tratamentos_registros_datatable">
<INPUT TYPE=HIDDEN NAME="IBIAPP_app" VALUE="cnisgestao_suporte">

But on MRE I don't know how to do. Reading the forum posts I found that I have to pass the following:

<input type="hidden" name="IBIMR_action" value="MR_RUN_FEX">
<input type="hidden" name="IBIMR_sub_action" value="MR_STD_REPORT">
<input type="hidden" name="IBIMR_domain" value="cnisgestao_suporte/cnisgestao_suporte.htm">
<input type="hidden" name="IBIMR_folder" value="#std_reports">
<input type="hidden" name="IBIC_server" value="v121d007">
<input type="hidden" name="IBIMR_fex" value="app/at_tratamentos_registros_datatable.fex">
<input type="hidden" name="IBIF_ex" value="app/at_tratamentos_registros_datatable.fex">
<input type="hidden" name="IBIMR_defer" value="" >
<input type="hidden" name="IBIMR_drill" value="RUNNID">

But I think I'm passing the wrong values on these parameters because when I run this .fex I get the error:

Error occurred. 
ERROR: MR_UNKNOWN_ERROR Item does not exist IBFS:/WFC/cnisgestao_suporte|app|at_tratamentos_registros_datatable.fex 

I think this final URL should be like: IBFS:/WFC/Repository/cnisgestao_suporte/std_reports/at_tratamentos_registros_datatable.fex. But I tried plenty of ways to pass these values on the HTML form and never reached this result. I think it's very strange those pipes ('|') instead of slashes ('/') too.

Using the Developer Studio, right click on the fex that I want to reference (properties) give me the following full path:

IBFS:/desenvolvimento/WFC/Repository/cnisgestao_suporte/std_reports/at_tratamentos_registros_datatable

Could someone help me? =]

This message has been edited. Last edited by: flavio.menezes,

Perhaps check the value you are setting for IBIMR_domain.

Per the 'WebFOCUS API Developer's Reference':

quote:

Required. The domain href is normally in the
form of an eight character domain directory
name, a slash, and an eight character
domain file name followed by an extension
(for example, domainon/domainon.htm or
untitled/untitled.htm).

Check the properties of the domain folder and you should see the value for 'Href'.

Using the Developer Studio, right click on the domain folder (properties) give me the following: http://img138.imageshack.us/img138/9740/4kih.jpg

I can't see the eight character domain directory name. =/

Everywhere is 'cnisgestao_suporte' as I wrote in the code.

Is there another way to get the eight character domain directory name?

quote:

8.0.02

Flavio, did you solve this?

Stuey,

What problems are you having?

T

quote:

Originally posted by stuey:

quote:

8.0.02

Flavio, did you solve this?

No, Stuey. I'm still having the same problem. I put the fex on EDASERVE so I can reference it. But I am not happy with this solution. =/

If you just require the URL then the folowing should suffice -

http://[server][:port]/ibi_apps/WFServlet?IBIMR_domain=[domainref]&IBIMR_folder=[folderref]&IBIMR_action=MR_RUN_FEX&IBIMR_subaction=MR_STD_REPORT&IBIMR_fex=app/[fexname].fex

Where the refs should be able to be seen when hovering the mouse pointer over the relevant component in Dev Studio view.

T

Hi guys,

It's possible to make the reference like this:

quote:

my fex

flavio, did you try just running the fex, from MRE, and then copying the entire string from your browser's address bar?
seems the easiest way to get the syntax correct.
Sure, you can write a link to appear any way you want...but that's just HTML basic.

<a href='...whatever' >my fex</a>

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

Flavio,
The best way to do this is using the REST API. See the doc services site for details. Note: This does require a license.

Now you can make straight servlet calls, but I would not use the views.bip URL example you provide as that can change between realizes. The same could happen with regular servlet calls, but is less likely. The REST license is getting you documentation and a guarantee that the calls will continue to work when you upgrade.