The following are known issues when using the Online Analytical Processing (OLAP) feature:

• Due to Internet Explorer browser behavior, closing an OLAP report before it completely loads may cause a WebFOCUS Reporting Server agent to abort.
• OLAP may stop responding when running Microsoft Internet Explorer 6.0 SP1 on Windows XP. To resolve this issue, you can download a Microsoft Internet Explorer fix from the Microsoft website.

  For more information about this issue, see Microsoft Knowledge Base Article 818506 at:

  http://support.microsoft.com/default.aspx?kbid=818506

• An OLAP internal message appears if a COMPUTE keyword is used after an ACROSS command. For example,

  TABLE FILE SALES 
  SUM UNIT_SOLD AND RETURNS 
  WHERE DATE GE '010' AND DATE LE '1031' 
  ACROSS DATE
  COMPUTE TOT_UNITS/D5=C1 + C3 + C5;
  COMPUTE TOT_RETURNS = C2 + C4 + C6; 
  END

• When saving an OLAP-enabled report that contains a graph in PDF format, the graph is not saved with the PDF report.
• An OLAP report that has been sorted using BY TOTAL will lose the BY TOTAL sort. As an alternative, use the Auto Sort button on the appropriate numeric column.
• The JavaScript version of OLAP no longer generates SET CODEBASE. No changes were made to the Stabilized Java Applet version of OLAP.

  If you receive the following message when you run an OLAP-enabled report, you will need to remove SET CODEBASE from the procedure to clear the message.

  (FOC209) THE DATA VALUE EXCEEDS ITS LENGTH SPECIFICATION: http://{your-ip-address}:80/ibi_html/javaassist

  The JavaScript version of OLAP will not remove this line if it is preexisting.

• OLAP is not supported with CGI or ISAPI and IWA security.
• When showing the OLAP filters on bottom (OLAPPANE BOTTOM), the OLAP selections pane appears below the report and it is not possible to select the values for the filters from the pane, as the list is dropped down and is not entirely visible. Use the OLAP filters on top (OLAPPANE TOP) to prevent this.