Oracle Application Express
3.1 Known Issues & Limitations
Return to Oracle APEX Home
Below is a list of known issues or limits with interactive reports and other 3.1 features. Whenever possible, a workaround is provided.
Known Issues/Limits with Interactive Reports
Actions Menu - Select Columns
  • The row length limit is 32K (just as with Classic Reports). You can include more columns but if too many are selected to be displayed, the user will get the following error - "ORA-06502: PL/SQL: numeric or value error: character string buffer too small".
Actions Menu - Filter
  • When using an "in" or "not in" filter, end users cannot include values that contain commas (because that is the delimiter between values). This includes data using a comma as their numeric decimal separator.
Actions Menu - Highlight {Theme 20 Only}
  • When using Theme 20 and a Cell Highlight, the background color is ignored. To workaround this issue do one of the following:
    1. Use Highlight Type of Row instead of Cell
    2. Use Highlight Type of Cell but leave the Background Color blank
    3. Switch from Theme 20 to one of the other Themes
Actions Menu - Chart
  • The maximum number of values shown in a chart is 1000. For pie charts, the maximum is 20 plus the "Other" slice. These limits cannot be changed.
  • Vertical Bar Chart - If your x-axis headings are large, every other heading may be suppressed (to avoid overlapping). The workaround is to change to a horizontal bar chart (which provides adequate space for the headings).
Actions Menu - Download
  • Not all Interactive Report settings are applied to CSV, PDF, etc., downloads. Specifically, the settings affecting the data and order are applied, but the ones that only affect formatting (control breaks, highlights, aggregates) are not.
Column Heading Menu
  • The maximum number of values shown in the column header dropdown list of values is 1000. This limit cannot be changed.
Application Builder (Developers Only)
  • Interactive Reports do not work with Oracle Database release
  • Interactive Reports will only work with supported browsers.
  • You can only have one Interactive Report display on a page at any given time.
  • The row length limit is 32k (just as with Classic Reports). You can include more columns but if too many are selected to be displayed, the user will get the following error - "ORA-06502: PL/SQL: numeric or value error: character string buffer too small". This should be considered when creating your report.
  • Developers cannot choose to disable highlighting for a column (they can selectively disable the other Actions Menu options).
  • The "Unique Column" entered by the developer to be used for the single row view is not validated. If the developer supplies a column that is not unique, the single row view will break.
  • Interactive Report queries cannot reference items whose values are set using the item "default" settings. The report will work on initial page load, but the AJAX functionality will break because the value is only set in memory for the initial page load, it is not in session state yet.
  • Certain queries (like those containing unions, group bys, distincts, and certain joins) will not return an associated ROWID pseudocolumn for each row. When creating interactive reports on queries like this, developers should either choose to disable the Single Row View or specify a different unique column to identify each row.
  • If you add columns to a query after it is initially created, they will not be displayed when the report is run. You will need to use the actions menu and either select the columns or click Reset.
  • Creating filters in interactive reports using links (as specified in the User Guide here) does not work correctly for the option LTE which returns GTE, or the option GT where the filter is not enabled by default.
  • Creating filters in interactive reports using links does not include all filter options, such as "Contains", "Between", "In", etc.
  • If you include an order by in your query and have the single-row view enabled, the order by will not be used. To overcome this, set a sort order when running the report and then save as the Default Report Settings.
Known Issues/Limits with Other 3.1 Features
Importing 3.1 Applications
  • Importing applications with multiple report queries and/or branches tied to print classic report regions fails. There are different workarounds available:
    1. When importing, enter the same Application ID as the original export's Application ID. If this is not posiible, then
    2. For the multiple report queries, after importing, go to Shared Components > Reports > Report Queries and select a different Report Layout from the select list and Apply Changes. Then modify the Report Query again and select the original Report Layout from the select list.
      For branches tied to print classic report regions, open the Print Attributes for the report and copy the Print URL. Then edit the Branch and paste the revised URL into the Target.
Classic Reports
  • When using the FILESIZE format mask on a numeric report colum (e.g. returns 100KB, 2MB, etc.), the sum of the column can not be computed.
  • When using the BLOB download format mask "DOWNLOAD", the download column must not be followed by a numeric or date column in the underlying SQL query. The workaround is to make the download column the last column or have it followed by varchar2 columns. This issue only applies to the SQL query, not the column display sequence in the report, which can be modified as needed.
  • In Application Express 3.0.x, report columns could be excluded when printing the report to PDF (or other formats), this is now also supported for CSV exports. If a column is defined as a link column, then this column is now automatically excluded from the export by design, however, currently this can't be reverted back, e.g. this type of column will always be excluded. The workaround, if you want to include the value from your link column in your export, is to duplicate that value in the query, include it in the export but hide it from the query.
Date Picker
Tabular Forms
  • For a tabular form that allows users to add new rows, all sortable columns should be set to sort NULLs last. If not (i.e. NULL values are shown first when sorting), when a user adds a new row, the row will be added to the first page of the tabular form but the user will be taken to the last page.