David Beagan

That's good to hear.

We've all done it.

In your fex report code, are you supposed to have: &PRODUCT_CATEGORY.QUOTEDSTRING; Are you missing the letter Y ? Or change your HTML to remove the Y.

Workaround could be to put the code TABLE FILE TBLMSTR_CALENDARPERIOD PRINT TBLMSTR_CALENDARPERIOD.TBLMSTR_CALENDARPERIOD.FISCALYEAR TBLMSTR_CALENDARPERIOD.TBLMSTR_CALENDARPERIOD.PERIOD WHERE TBLMSTR_CALENDARPERIOD.TBLMSTR_CALENDARPERIOD.ROLLINGMONTHS EQ -4; ON TABLE HOLD AS HOLDFYPERIOD END -RUN -READFILE HOLDFYPERIOD -DEFAULTH &FISCALYEAR = '' -DEFAULTH &PERIOD = '' In one fex, and then have it -INCLUDE the code from your main GUI report.

What does your code do correctly and what does not work?

Maybe SCROLLHEIGHT=AUTO, would help? TABLE FILE GGSALES SUM UNITS DOLLARS BY REGION BY ST BY CITY BY DATE ON TABLE SET SHOWBLANKS ON ON TABLE SET BYDISPLAY ON ON TABLE SET PAGE NOLEAD ON TABLE SET STYLE * TYPE=REPORT, BORDER=LIGHT, BORDER-COLOR=RGB(220 220 220), FONT=ARIAL, HFREEZE=ON, SCROLLHEIGHT=AUTO, $ TYPE=TITLE, BACKCOLOR=RGB(220 220 220), $ TYPE=DATA, BACKCOLOR=(BY=B3 RGB(245 245 245) WHITE), $ END The scrollable area will expand vertically for the size of the iframe. Or if the rows all fit in the iframe then no scroller.

Is the report freezing the column titles? It would have HFREEZE=ON in the report's style sheet.

The columns in my example are not sorted in quite the right order. You can change that by using extra leading spaces on the decoded values.

Yea, Clayton, that's it. I tested it out, and the ROW-TOTAL causes the issue.

Is CLM_RESET_TRACKING_SQL_CLU.PERC_OF_PD_TTL_RESET a compute that is calculated in your master file? What is the computation? Maybe it is a deficiency of WebFOCUS that it doesn't treat this like an actual compute coded in the fex.

This would appear to work. Have you tried it? TABLE FILE ggsales SUM UNITS DOLLARS COMPUTE Pct/P8.2% = UNITS / DOLLARS * 100; BY REGION ACROSS CATEGORY RECOMPUTE ON TABLE SET PAGE NOLEAD END

I made a sample data set, current_open_requests, to try this. The basic approach to producing this kind of report is to calculate a TIMERANGE field based on the REQUESTED_ON field. Then use that TIMERANGE field to make ACROSS columns. The following code illustrates this. SET PAGE=NOLEAD DEFINE FILE current_open_requests HOUR/HH = REQUESTED_ON; HOURA5/A5 = FPRINT(HOUR,'HH','A5'); TIMERANGE/A7 = DECODE HOURA5 ('07' ' 7am' '08' ' 7am' '09' ' 7am' '10' ' 7am' '11' '11am' '12' '11am' '13' '11am' '14' ' 2pm' '15' ' 2pm' '16' ' 2pm' '17' ' 5pm' '18' ' 5pm' '19' ' 5pm' ELSE 'other'); END TABLE FILE current_open_requests SUM CNT.SEQ_NO BY STATUS AS '' ACROSS TIMERANGE AS '' ON TABLE SET PAGE NOLEAD END The output from this code

When you say "filter by specific time frame" are you referring to creating the columns 7am 11am 2pm 5pm ?

Thanks AJB. Will there be documentation on Hyperstage?

We will be confronting this issue in the coming months. You would think this would be documented. I couldn't find any documentation.