Can the Pre-Process fex reside in MRE, or does it need to be on the data server/ app folder? If MRE, then how is it identified?

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

Shouldn't this work as long as the results are the same as the burst field (the 1st by field is REPORT_NAME)? This displays the results in XLM format when executed directly from the app folder.
CODE:

SET MSG = ON
TABLE FILE {filename}
PRINT REPORT_NAME/A35 AS 'VALUE'
      REPORT_NAME/A35 AS 'DEST'
BY    REPORT_NAME NOPRINT
WHERE LOCATION_LEVEL EQ 'DIV'
ON TABLE SET HOLDLIST PRINTONLY
ON TABLE SET ASNAMES ON
ON TABLE PCHOLD
END

Results, only the 1st and last (10th) records are displayed:

  <?xml version="1.0" encoding="UTF-8" ?> 
- <fxf version="1.0" data="hold">
- <report records="10" lines="10" columns="2" rows="10">
  <target format="" version="" type="" destination="HOLD" /> 
- <column_desc>
  <col colnum="c0" fieldname="VALUE" alias="E01" datatype="char" width="35" focus_format="A35" description="" accept="" help_message="" title="Report Name" property="" reference="" valign="left" /> 
  <col colnum="c1" fieldname="DEST" alias="E02" datatype="char" width="35" focus_format="A35" description="" accept="" help_message="" title="Report Name" property="" reference="" valign="left" /> 
  </column_desc>
- <table>
- <tr linetype="data" linenum="1">
  <td colnum="c0">rs140418rec1.pdf</td> 
  <td colnum="c1">rs140418rec1.pdf</td> 
  </tr>
. . .
- <tr linetype="data" linenum="10">
  <td colnum="c0">rs140418rec9.pdf</td> 
  <td colnum="c1">rs140418rec9.pdf</td> 
  </tr>
  </table>
  </report>
  </fxf>

BTW:
1) This works in WebFOCUS 7x.
2) When the disribution is set to "Single email address" the email is delivered with all the 10 attachments as expected. This drew me to a conclusion that it's not a bursting issue, just the dynamic distribution list creation.

Hi Doug,

I've consulted with the product manager on this. First, a pre-process fex cannot reside in MRE. It must be on the server. That doesn’t seem to be the issue here though.

Can you please provide more detail about the scheduled fex, the pre process and the expected and actual behavior?

Is the problem that the same report returns different output in 7 vs 8?

Thanks and regards,

Kathryn

It sounds like taht answers the question.
Thanks Kathryn