Skip to Main Content

Info

On Apex 4.2.2 the Empno 1 LOV gives this type of error:
Apex 5.1.1 (or maybe earlier versions than that) seems to have fixed this, but I thought I'd include this for posterity.

The Empno 2 LOV shows a rewrite of the query that works fine with Apex 4.2.2. Basically, avoid the combination of a With clause and a Pipelined table function.
Note that not all LOV types seem to be affected. When I tried this, Popup LOVs gave the error, while e.g. Select Lists worked fine.

Settings

Code

Page

Identification
Page ID
Name

Item

Identification
Sequence
Name
Display As
User Interface
Region
List Of Values
Display Extra Values
Display Null Value
List of values definition
Advanced
Warn on Unsaved Changes
Source
Source Used
Source Type

Item

Identification
Sequence
Name
Display As
User Interface
Region
List Of Values
Display Extra Values
Display Null Value
Cascading LOV Parent Item(s)
List of values definition
Advanced
Warn on Unsaved Changes
Source
Source Used
Source Type

Item

Identification
Sequence
Name
Display As
User Interface
Region
List Of Values
Display Extra Values
Display Null Value
Cascading LOV Parent Item(s)
List of values definition
Advanced
Warn on Unsaved Changes
Source
Source Used
Source Type

Package

Package
Name
Source

Package Body

Package Body
Name
Source