I am trying to do a conditional include based on the input of a dropdown box. I used some code I found in the forum, but it is not working.

This code is in the parent fex:
-SET &REPORTTYPE = &RTYPE.(,,).REPORTTYPE.;
-SET &DATASET = IF '&REPORTTYPE' EQ 'PRICING' THEN 'MLAPMETRICSORT1.FEX' ELSE 'MLAPMETRICSORT.FEX';


Then in a fex that I am including I make the reference:
-MRNOEDIT -INCLUDE &DATASET

I do not get an error, just no data shows up. If I hard code one fex or the other like:
-INCLUDE MLAPMETRICSORT1.FEX

it works.

Any help would be appreciated.

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

Try -INCLUDE &DATASET.EVAL but even that may not work - embedding amper variables in an INCLUDE statement isn't kosher.

I would do it this way:

-IF &REPORTTYPE EQ 'PRICING' GOTO SORT1 ELSE GOTO SORT;

-SORT1
-MRNOEDIT -INCLUDE mlapmetricsort1.fex

-GOTO SORTEND

-SORT
-MRNOEDIT -INCLUDE mlapmetricsort.fex

-SORTEND

Try using the app folder name and then the fex since that is how the GUI does it:

 
-SET &DATASET = 'yourappfolder/mlapmetricsort1.fex';
-MRNOEDIT -INCLUDE &DATASET
 

I know it works for htmlform at least

EDIT: It does work for fexes as well.

BTW when doing an htmlform with the MRNOEDIT, I do not run into the 8 character limit for file names using htmlform. Hmm...

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

I am going to try Francis' solution.
J, I have tried the app folder and same issue.
Thanks for the replies.

Sorry to hear that... maybe a 7702 thing.


Have you tried through the GUI to get the correct syntax for an INCLUDE outside of the MRE? Maybe its a little different in your version?

I haven't tried that yet, but Francis solution is going to work fine for what I am doing. Thanks for the replies.

Hold on a sec. If I just hardcode -INCLUDE myfile.fex, it does not work because the file is in the apps folder

If plain old -include yourfex.fex is working, the fex must be in the MRE.

Try:

 
-SET &DATASET = 'app/mlapmetricsort1.fex';
-INCLUDE &DATASET
 

It is good practice to avoid GOTO's as much as possible.

quote:

-SET &DATASET = 'app/mlapmetricsort1.fex';
-INCLUDE &DATASET

That is one that I have tried. Get this error:

ERROR: ERROR_MR_FEX_NOT_FOUND Can't create item object based on provided item key &DATASET.fex.

Looks like you are right. The original solution I wrote works if the fex is in dataservers and the HTML is in the MRE but not if both of them are in the MRE. This seems vaguely familiar.

The same goes with the htmlform 8 character limit. The limit only applies if the html page is in the MRE.

Of course not. An MRE-type -INCLUDE is resolved in the client, where & is just another character. &var substitution only happens on the back-end (webfocus reporting) server.

quote:

An MRE-type -INCLUDE is resolved in the client, where & is just another character. &var substitution only happens on the back-end (webfocus reporting) server.

So, what does that mean?

So we won't have this issue in v.8 then?

Francis:

clarification

J, thanks for the link to the MRNOEDIT explanation.

Now, how does it apply to code like this:

-MRNOEDIT -INCLUDE &DATASET

Because of -MRNOEDIT, MRE will not evaluate the Dialogue manager variable, but will the reporting server evaluate -INCLUDE &DATASET?

If you tie what j.gross says and what the wordy link I sent you says, it makes sense. Mavericks solution won't work because the include is handled client side.

Because of that, he tried to use the MRNOEDIT feature to handle it on the back end. However, the file he was referencing is located in the MRE, so the reporting server knows nothing about it. If it was located in the data servers section, there wouldn't be an issue.

I think this whole thing goes away in 8 since everything is in one repository. Or have the little birds been lying to me all along.

In WebFOCUS 8, you can still have fexes residing in app folders on the reporting server...

They did lie to me. It is the authentication that is centralized...

I also heard something about getting rid of domains and security is based on tabs for the portal?

quote:

Originally posted by Francis Mariani:
...I would do it this way:

-IF &REPORTTYPE EQ 'PRICING' GOTO SORT1 ELSE GOTO SORT;

-SORT1

-MRNOEDIT -INCLUDE mlapmetricsort1.fex

-GOTO SORTEND

-SORT
-MRNOEDIT -INCLUDE mlapmetricsort.fex

-SORTEND

So would I, if they're stored in MR repos.

Just bear in mind, both of the MR includes will be expanded and sent up to the server (and down again, to the browser, for a round trip, if autoprompting kicks in). If they contain any labels (for GOTO or REPEAT), make sure they are unique across the two (or however many) included MR fex files + the main fex.

An alternate solution:

Move the dynamics of which report to invoke out of MR, into the province of the back-end Reporting Server.

* create a little driver fex on the reporting server (not in MR repository), in the same APP folder as the two report fex files;

* hard-code its name and location in the -MRNOEDIT -INCLUDE

* have the driver fex invoke the appropriate report fex (based on the &REPORTTYPE parameter). Note that the -INCLUDE in the driver should not have -MRNOEDIT, since it is stored on the reporting server.