Oracle APEX

Known Issues - APEX 18.1.0

APEX 18.1.0 was released on May 24, 2018.

Please review the Release Notes for significant issues known at time of release. Any new significant issues will be added here. This page was last updated on August 27, 2018.

Note: Review the APEX 18.1 Known Issues Addendum for important information regarding flash charts.

  • 28550442 - ORDS REST WORKSHOP PARAMETERS NOT PROVIDING 'RESPONSE' TYPE
    Within Oracle APEX ORDS REST Workshop you can not specify the correct parameter types in the Handler. Using SQL Developer or PL/SQL APIs you can specify HEADER, URI (IN parameter only), or RESPONSE (OUT parameter only). Within Oracle APEX you can only specify URI or HEADER, irrespective of whether it is an IN or OUT parameter, and you can not specify a RESPONSE parameter.
    Workaround: Maintain REST services with RESPONSE type parameters using SQL Developer or PL/SQL APIs.
  • 28333648 - CLASSIC REPORT WITH GENERIC COLUMNS THROWS ORA-01403 IF COLUMNS NAMED "COLNN"
    When a classic report is based on a PL/SQL function returning SQL query and has Generic Columns enabled, the generated SQL query returns column names COL01 .. COL50 (like the generic column names). Such a report will fail to render and throw an ORA-1403 error.
    Solution: A PSE has been made available for this issue on MyOracleSupport. Navigate to Patches & Updates and search for patch number 28128115. Note this PSE also contains other bug fixes, please review the README in the patch for more details.
  • 28439164 - JSON ERROR ON DYNAMIC ACTION WHEN ACTION CODE IS USING APEX_JSON
    When using the APEX_JSON.WRITE% procedures in a dynamic action of type "Execute PL/SQL Code", the browser always displays a JSON error message.
    Solution: A PSE has been made available for this issue on MyOracleSupport. Navigate to Patches & Updates and search for patch number 28128115. Note this PSE also contains other bug fixes, please review the README in the patch for more details.
  • 28267010 - INTERACTIVE REPORT COL HDR FILTER DROPDOWN DOES NOT RESPECT "ESCAPE SPECIAL CHARS"
    In APEX interactive reports, the list of values which is automatically generated for the column heading filtering does not respect the columns' "Escape special characters" attribute. It always escapes the content.
    Solution: A PSE has been made available for this issue on MyOracleSupport. Navigate to Patches & Updates and search for patch number 28128115. Note this PSE also contains other bug fixes, please review the README in the patch for more details.
  • 28333520 - CLASSIC REPORT USING GENERIC COLUMNS AND HAVING "COMPUTE SUM" ENABLED CAN THROW ORA-1403 ERROR MESSAGE
    A classic report (based on a PL/SQL function returning a SQL Query) with Generic Columns set to Yes can throw an ORA-1403 error when the following prerequisites are met: Generic Column Count matches exactly the number of selected columns; and Compute Sum is enabled on at least one column
    Solution: A PSE has been made available for this issue on MyOracleSupport. Navigate to Patches & Updates and search for patch number 28128115. Note this PSE also contains other bug fixes, please review the README in the patch for more details.
  • 28325138 - APPLICATION IMPORT FAILS WITH ORA-1403 WHEN WEB SOURCE MODULES USE A REMOTE SERVER FOR AUTHENTICATION
    Importing an application export from APEX 18.1 with Web Source Modules fails with ORA-1403 when the following conditions are met: At least one Web Source Modules uses OAuth Authentication; and A separate remote server is used for Authentication (Shared Components > Web Source Modules > Authentication > Authentication Server. This error is raised as the authentication server is not being added to the export file.
    Solution: A PSE has been made available for this issue on MyOracleSupport. Navigate to Patches & Updates and search for patch number 28128115. Note this PSE also contains other bug fixes, please review the README in the patch for more details.
  • 28349551 - APEX VIEWS APEX_APPL_WEB_SRC_PARAMETERS AND APEX_APPL_WEB_SRC_COMP_PARAMS CONTAIN NO ROWS
    The data dictionary views listed do not return any rows, even if Web Source Parameters are present.
    Solution: A PSE has been made available for this issue on MyOracleSupport. Navigate to Patches & Updates and search for patch number 28128115. Note this PSE also contains other bug fixes, please review the README in the patch for more details.
  • 28420025 - WEB SOURCE MODULE IGNORES DECIMAL CHARACTERS FOR NUMBER VALUES WHEN USED WITH APEX_EXEC OUTSIDE AN APEX APPLICATION
    When using a web source module outside the context of an APEX application, using the APEX_EXEC package, decimal characters are being ignored for NUMBER columns.
    Solution: A PSE has been made available for this issue on MyOracleSupport. Navigate to Patches & Updates and search for patch number 28128115. Note this PSE also contains other bug fixes, please review the README in the patch for more details.
    Workaround: Set wwv_flow.g_nls_decimal_separator to the current decimal character before invoking the APEX_EXEC procedures, for example:
    begin
      wwv_flow.g_nls_decimal_separator := substr( to_char( 1/2, 'TM9' ), 1, 1 );
    end;
  • 28320098 - INTERACTIVE REPORT FILTER THROWS ORA-12728 IN FR-CA LOCALE WHEN DATE COLUMN IS PRESENT
    When an APEX application runs in the FR-CA locale and an interactive report has a DATE or TIMESTAMP column, the Interactive Report filter dialog does not render correctly, instead the AJAX request throws an ORA-12728 error.
    Solution: A PSE has been made available for this issue on MyOracleSupport. Navigate to Patches & Updates and search for patch number 28128115. Note this PSE also contains other bug fixes, please review the README in the patch for more details.
  • 28013850 - WEB SERVER ERRORS BECAUSE OF NON-COMPLIANT SPECIAL CHARS {} IN URL
    Some web servers (e.g. Tomcat 9.x) are raising errors for special characters like "{" and "}" that can appear in APEX URLs.
    Solution: A PSE has been made available for this issue on MyOracleSupport. Navigate to Patches & Updates and search for patch number 28128115. Note this PSE also contains other bug fixes, please review the README in the patch for more details.
  • 28202781 - INTERACTIVE GRID IN TRANSLATED APP GIVES ERROR ON UPGRADE
    The text string for APEX.IG.SUMMARY was changed to have fewer parameters in APEX 18.1. Translated applications that utilize this string will raise a JavaScript error at runtime.
    Workaround: Supply a correct translation for this text string.
       KEY: APEX.IG.SUMMARY
       TEXT: Interactive Grid. Report: %0, View: %1.
  • 28077007 - FEEDBACK IS ENABLED IN THE ORACLE APEX 18.1 DISTRIBUTION
    Developers will be able to click on the feedback link within the Oracle APEX development environment. Any feedback logged will be inserted into the feedback tables, viewable from Team Development.
    Workaround: There is currently no workaround. Please check back on this page as we will make a PSE available as soon as possible.
  • 28076798 - UNBLE TO SCROLL TREES AND DIALOGS USING TOUCH
    For both new apps created in Oracle APEX 18.1 and those upgraded from earlier releases, various components including trees, navigation menus, and any dialog windows can not scroll once touch is enabled.
    Workaround: A simple workaround is to use two fingers to scroll within the affected components. Please check back on this page as we will make a PSE available as soon as possible.
  • 28076993 - ORDS REST WORKSHOP CURRENTLY UNABLE TO HANDLE LARGE SCRIPT SIZES
    Currently the ORDS REST Workshop is unable to handle script sizes of over 32K. Due to the potentially large number of Templates a module might have and the fact that ORDS requires a full module and all children to be re-created if a module level change takes place, these scripts could grow far over 32k. This affects all code executed by the ORDS Screens and the import of ORDS Services.
    Workaround: Only define a small number of templates in each module. For existing modules that are raising errors, export the module in question, manually edit the export file to make required changes, and then use the Oracle APEX Script Runner to run the updated script back in.
  • 27971759 - APEX_APP_SETTING.SET_VALUE NOT VALID VALUE ERROR IF VALID VALUE IS NULL
    Trying to change an application setting value using APEX_APP_SETTING.SET_VALUE raises misleading error message, "Not Valid Value", if valid value is NOT defined in the application setting. "Not Valid Value" error should raise only if valid values are defined.
    Workaround: There is currently no workaround.
  • 28035049 - ISSUE AUTHENTICATING TO ORDS OAUTH2 MANAGEMENT SCREENS USING APEX USER
    Users are unable to use APEX users to secure/authenticate ORDS Based REST Services using OATH2. ORDS Uses www_flow_listener.authenticate to try to authenticate the user, but this package is being blocked by www_flow_epg_include_modules.authorize_in_apex as it is not “white listed”.
    Workaround: There is currently no workaround.
  • 28075855 - REGRESSION: MISSING SUBSTITUTION OF REGION SQL QUERY
    Substitution Variables (&NAME.) contained in the SQL Query of the Region Types Calendar, Tree, Column Toggle Report, List View, Reflow Report and Custom Region Type Plug-ins are not substituted when the SQL Query gets executed. The following example is supposed to return a URL for the current application:
    select empno,
    ename,
    'f?p=&APP_ID.:26:' || :APP_SESSION || '::&DEBUG.:26:P26_EMPNO:' || empno as edit_link
    from emp
     However, due to the bug, &APP_ID. and &DEBUG. will not get replaced.
    Solution: A PSE has been made available for this issue on MyOracleSupport. Navigate to Patches & Updates and search for patch number 28128115. Note this PSE also contains other bug fixes, please review the README in the patch for more details.
    Workaround: Use bind variables instead of substitution variables. This is a good security best practise anyway, to avoid SQL injections. Note: The above code isn't vulnerable for SQL injection, because &APP_ID. and &DEBUG. are safe substitution variables.
    select empno,
    ename,
    'f?p=' || :APP_ID || ':26:' || :APP_SESSION || '::' || :DEBUG || ':26:P26_EMPNO:' || empno as edit_link
    from emp
     or
    select empno,
    ename,
    apex_page.get_url (
       p_page => '26',
       p_clear_cache => '26',
       p_items => 'P26_ID',
       p_values => empno ) as edit_link
    from emp
  • 28012212 - CANNOT IMPORT AN APP IF EXPORT FILE INCLUDES PUBLIC IG REPORTS
    If an application export includes public interactive grid reports, the import to replace an application will fail with the following error:
    ORA-00001: unique constraint (APEX_180100.IG_RPT_NAME_UK) violated.
    Workaround: Exclude public reports when exporting an application. If there is a need to move public reports to upgrade an application, save those public reports as alternative default reports to avoid the error.

Changed Behavior:

  • N/A - FLASH CHARTS AND GANTT CHARTS NO LONGER DISPLAY
    Starting with Oracle Application Express 5.1.4 and continuing with Oracle APEX 18.1, the AnyChart and AnyGantt flash .swf files have been removed from the /images folder. This will result in your map chart and gantt charts no longer rendering. No error message will be displayed, instead the region will be blank.
    Solution: To install the AnyChart Flash Content in your instance, download the zip file, unzip the contents and follow the instructions outlined in the README.txt file, to update your images folder.
    Workaround: Please see the Addendum for more details.
  • N/A - JQUERY AND JQUERY UI UPGRADE
    Oracle APEX 18.1 includes jQuery 3.1.1, which breaks compatibility with earlier 2.x versions. If your application relies on removed 2.x, or 1.x jQuery functionality, then this functionality will no longer work.
    Workaround: For applications that still rely on removed 2.x functionality, you can use the jQuery Migrate plug-in. To include this plug-in, set the Desktop User Interface Details attribute Include jQuery Migrate to Yes.
    If your application relies on removed 1.x jQuery APIs, that functionality will no longer work, and you must update the JavaScript to only use jQuery 3.1 APIs.
    Review the jQuery migration guides to learn more: For further information including information about the jQuery UI upgrade, please review section 8.1.2 Known Issues for jQuery and jQuery UI in the release notes.
  • N/A - CLASSIC REPORTS: ENABLING COMPUTE SUM AND BREAK COLUMNS CAN LEAD TO SQL ORDER BY CLAUSE BEING IGNORED
    The Compute Sum functionality in classic reports does now use the SUM() OVER() analytic SQL function. If Compute Sum and Break Columns are enabled and the report query contains an ORDER BY clause, the analytic SQL function can lead the database query optimizer to ignore the ORDER BY clause.
    Workaround: Use the Sorting > Default Sequence column attribute to control report sorting.
Downloads