Open Bugs and Known Issues

10 Open Bugs and Known Issues

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

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-261-known-issues/

Alternatively, you can view the Accessibility Conformance Report (ACR). The ACR includes details of all known issues with APEX. A single release of APEX uses multiple component ACRs for specific areas of the product (for example, "Development Environment", "Components", "Documentation", etc.) Please go to Accessibility ACRs | Oracle's Accessibility Program to find the ACRs for Oracle APEX.

10.1 Known Issues for Importing APEXlang Applications in App Builder

Preinstallation App Subscription Mapping

Before importing an APEXlang application that uses a master application subscription, you can update deployments/default.json to modify the subscription mapping. This is only necessary when the destination subscription mappings differ from what is in the defaults.json file.

For example, suppose you installed a master application with id 101 into a target environment and assigned it a new id 901. Before installing a subscribing app id 102 in the target, edit its default.json to adjust the value of the "101" property key in the subscription.masterApps object. Change the value to 901 as shown below:

{
  "app" : {
    "id" : 102
  },
  "subscription" : {
    "masterApps" : {
      "101" : 901
    }
  }
}

Then, your attempt to import application 102 that subscribes to components in the master app whose id was changed in the target to 901 will find its master application components as expected:

SQL> apex import -input subscribing-app

Post-installation Credentials and Remote Servers

After successful APEXlang app import, in this release, no convenience page appears to configure "Prompt on Install" Web Credentials or Remote Servers. To adjust them if necessary, use the corresponding edit page in Workspace Utilities.

Importing APEXlang for Working Copy

Importing an APEXlang application export into a working copy disassociates the working copy from its base application.

10.2 Known Issues for Workflow Component

The known issues for the Workflow Component are:

APEXlang import throws a validation error when the application contains a workflow with a Parallel Branch activity.

10.3 Known Issues for Working Copy Feature

The known issues for the working copy feature are:

Importing an APEXlang application export into a working copy disassociates the working copy from its base application.
Server Error message - If you are running APEX on Oracle Database release 19c and using the new working copy feature, when you choose the actions Merge into Main or Refresh from Main or Compare Changes, you may get a "Server Error" message that is caused by an underlying ORA-00600 error message. For example:
```
ORA-00600: internal error code, arguments: [qjsnplsDecDomRefCnt:noValP], [], [], [], [], [], [], [], [], [], [], []
```
The fix for this error is to upgrade to 19.16 or higher.
ORA-00001 error during merge - The Working Copy feature raises an ORA-00001 unique constraint error when attempting to merge changes for component names that are not unique. It is important to coordinate the naming of shared components across working copies and the main application to avoid this error occurring.

10.4 Known Issues for ACL Roles

After creating a role, change the automatically-generated lowercase static ID to uppercase. This ensures apex_acl.user_has_role evaluates correctly.

10.5 Known Issue with Theme Decoupling

There is a known issue with theme decoupling in the following scenario:

A Master theme app and a child theme app are defined in the same workspace.
The Master theme app is subscribed to the UT in the central application, and the child theme app is subscribed to the Master theme app.
The Master theme app hosts some locally-defined templates that don't exist in the central application.

In this scenario, if you refresh the child app theme, it does not copy the Master theme's locally-defined templates over to the child app. As a workaround, you can copy the locally-defined templates manually.

10.6 Known Issues with Using BOSS REST Services

Total Results Only Works with Search Views

BOSS support for total results currently only works on search views.

Error Defining REST Data Source Against OAuth-Protected BOSS Endpoint in RDBMS 19c

If your APEX is running in an Oracle 19c database, then when initially defining a REST Data Source against an OAuth-secured BOSS endpoint, you may encounter an HTTP 401 Not Authorized error when discovering the service. The error text returned could indicate Anonymous Access is not allowed for OpenApi Service.

The solution is to use the fully-qualified BOSS endpoint URL including both the optional language path segment (for example, $en) and an explicit deployment id after the version path segment. For example, instead of referencing .../v1/exampleobject you would use .../v1:99/$en/exampleobject during discovery. Once the REST Data Source is created, you can edit its service URL to remove the language path segment and the explicit deployment id.

10.7 Known Issue with ORDS 24.1 and APEX SQL Developer Web

When on an upgraded APEX 24.1 instance using ORDS version 24.1.0, if you click the link from APEX App Builder to SQL Developer Web, an error message ("Method Not Allowed") appears.

This bug is fixed in ORDS version 24.1.2.

10.8 Known Issue for Sublists

Currently, sublist entries are not included in list search results when the list search configuration is defined on the list referencing the sublist. This will be fixed in a future release.

10.9 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.

10.10 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.

10.11 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/

10.12 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.

10.13 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.

10.14 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.