<af:query> Component Caches Results From Previous Search When Used In Dynamic Region
(Doc ID 2812343.1)
Last updated on NOVEMBER 01, 2022
Applies to:
Oracle JDeveloper - Version 12.2.1.4.0 to 12.2.1.4.0 [Release 12c]Information in this document applies to any platform.
Symptoms
In an ADF 12.2.1.4.0 application, when <af:query> component with table is used in a Bounded Task Flow dropped as a dynamic region in a page, the results from a prior search are cached.
The filter is removed from the <af:query> component, but the table still caches the previously filtered results.
The same scenario does not show caching issues with ADF 12.2.1.3.0.
Changes
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 |
| Changes |
| Cause |
| Solution |
| References |