"Access Mode" = "Range Paging" Causes Error '<makeCurrent> ADFv : no row found for rowKey'

(Doc ID 1287174.1)

Last updated on MARCH 08, 2017

Applies to:

Oracle JDeveloper - Version: and later   [Release: No Release Description and later ]
Oracle JDeveloper - Version: and later ]
Information in this document applies to any platform.


When using a View Object defined with the Tuning option "Access Mode" set to
"Range Paging" or "Range Paging Incremental" in an af:table, and when the end user selects a
record outside the current range paging,  the current row will not be correctly set and the following
error will be displayed in the Logs:
<FacesCtrlHierBinding$FacesModel> <makeCurrent> ADFv : no row found for rowKey : [oracle.jbo.Key[<Key Attribute for Selected Row> ]].

This can be easily reproduced by setting the "Access Mode" set to "Range Paging" and
Range Size = "1"

When selecting different rows in the table, you'll then see the errors:
<FacesCtrlHierBinding$FacesModel> <makeCurrent> ADFv : no row found for rowKey : [oracle.jbo.Key[2 ]]
<FacesCtrlHierBinding$FacesModel> <makeCurrent> ADFv : no row found for rowKey : [oracle.jbo.Key[3 ]]


Sign In with your My Oracle Support account

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

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms