Open Bugs and Known Issues

11 Open Bugs and Known Issues

This section describes bugs and known issues for Oracle APEX release 22.2.

Tip:

This section is current as of the writing of this document. To view the most current listing of changed behavior, go to the Known Issues page:

https://www.oracle.com/tools/downloads/apex-downloads/apex-222-known-issues.html

11.1 Known Issue with Confirm or Alert Dynamic Action Messages When Upgrading

Issue

When upgrading from APEX 21.2 or earlier, the text in existing Confirm or Alert dynamic action messages may be truncated if it is too long, leading to data loss. This is due to APEX HTML-escaping messages, which may increase their size past the 4000-byte limit.

Resolution

Prior to upgrading, run a query to check whether any messages are affected:

select *
    from apex_application_page_da_acts
where action_name in ('Alert', 'Confirm')
    and ( lengthb( attribute_01 )
        + ( 4 * nvl( regexp_count( attribute_01, '&|"|<|>' ), 0 ) )
        ) > 4000;

If the query does not return any rows, proceed with the upgrade.

If the query does return rows, convert the affected rows into application text messages and reference them with substitution syntax before proceeding with the upgrade.

11.2 Known Issue using 'Source Display' region type plug-in in previously installed Sample Apps

Issue

The Source Display region type plug-in that is used in a Sample App installed in a previous release of APEX no longer works. This issue is due to the removal of views associated with AnyChart charts and AnyMap map charts.

Resolution

Open the application to edit it.
Navigate to Shared Components, under Other Components select Plug-ins, and Source Display.

Update the PL/SQL Code to remove the following lines of code (lines 35 - 48):

union all
select reg.source_type, fs.series_seq, fs.series_name, fs.series_query source
from apex_application_page_regions reg,
    apex_application_page_flash5_s fs
where reg.application_id = :APP_ID
    and reg.page_id = :APP_PAGE_ID
    and reg.static_id = d_region_static_id
    and fs.application_id = reg.application_id
    and fs.page_id = reg.page_id
    and fs.region_id = reg.region_id
    and reg.source_type in (
        'Flash Chart',
        'Map'
    )

Click Apply Changes.

11.3 Known Issues for jQuery Upgrade

jQuery 3.x breaks compatibility with earlier 2.x versions. 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 no longer works as of Application Express release 18.1. You must update the JavaScript to only use jQuery 3.5 or later APIs. See the jQuery migration guides to learn more:

To migrate from 1.x to 2.x see http://jquery.com/upgrade-guide/1.9/
To migrate from 2.x to 3.5.x see https://jquery.com/upgrade-guide/3.5/

11.4 Interactive Grid support for REST Enabled SQL

Issue

Oracle REST Data Services (ORDS) REST Enabled SQL has a limit of 1000 bind variables in a REST Enabled SQL request. As a result, when Interactive Grid DML sends more than 1000 column values, the following error displays: "Internal ORDS OUT Bind limits exceeded."

Solution

Reduce the amount of DML rows.

11.5 Group By Component Type mode prevents Default View

Issue

Due to the removal of "Sort by Processing Order" and "Group by Component Type" from Page Designer, developers may be stuck in "Group by Component Type" mode without a way to switch back to the default view ("Sort by Processing Order").

Resolution

In Page Designer, open Developer Console in the browser, and run the following command:
```
pageDesigner.saveBoolPref( "GROUP_BY_COMPONENT_TYPE", true );
```
Refresh the page.

11.6 Known Issues for Data Generator

There are known issues with the API for the data generator:

API does not accept Percent Blank value of 100.
Some built-ins that return a number data type ignore values set for minimum value, maximum value, and value precision.
Preview ignores columns when all their values are null.
When generating data and using row scaling other than 1x, sometimes an extra row is added.

These issues will be fixed in a future release.

11.7 Known Issue Using Readable Export Format

The Readable Export Format in JSON and YAML does not include attribute values for plug-ins, themes, and templates.

This will be resolved in a future release of APEX.