My Oracle Support Banner

APEX Bind Variable :App_region_id Does Not Work In Authorization Scheme's Exists SQL Query (Doc ID 2706831.1)

Last updated on SEPTEMBER 02, 2020

Applies to:

Oracle Application Express (APEX) - Version 19.2 and later
Information in this document applies to any platform.

Symptoms

In APEX 19.2 version the APEX bind variable :app_region_id does not work in an authorization scheme's exists SQL Query/
The bind variable :app_region_id works in the classic report Region's sql statement :

Select WORKSPACE, APPLICATION_ID , PAGE_ID, REGION_ID, REGION_NAME,AUTHORIZATION_SCHEME, :app_region_id from apex_application_page_regions where region_id = :app_region_id.

The query returns the data set for the region only.
However if the bind variable is used for Authorization scheme it does not return any records.

Authorization scheme setting >

Scheme type: Exists SQL Query SQL
Query for schema: Select 1 from apex_application_page_regions where region_id = :app_region_id;

As soon as the region's authorization is set to that authorization schema it is not displayed Application export is available.

The problem is app_region_id cannot be used in the authorization scheme as it is not a global variable.

However there is a requirement for APEX_REGION to be a global variable in order to do APEX region authorization.

 

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.