Sub Query Workarounds for ADF View Object Design Time Issues in JDeveloper

ADF/JDeveloper 12.2.1.3

In this blog, I will show some workarounds for some specific issues we may see in JDeveloper View Object Wizard

When we are designing a View Object in JDeveloper, especially when we modify the query in the expert mode, in some cases as mentioned below, the wizard does not build the attribute mappings as expected.

• When the Query has an 'extract' clause
• When the Query has a table or view accessed from a DBLink 
• When the Query has a synonym for an object from another Schema

We normally see this behavior when we join attributes from tables with one of the above. 

A General Workaround for these kind of issues is to use a Sub Query. 

• When we use Extract clause in the query to get an attribute, the attribute is not shown as a selected attribute in the Attribute Mappings. This issue comes especially when we join the ‘extract’ attribute with other attributes

• When we query a table via a DB Link the attributes from the DB Link are not shown in the ‘Attribute Mappings’. This issue comes especially when we join the ‘dblink’ attributes with other attributes

• When we query columns from a partitioned table the attributes are not shown in the Attribute Mappings. Below table is partitioned on ‘payroll_date’.This happens especially when we join the attributes with other table attributes.Other best option in this case is if the table is in a different Schema, then we may have to give the Owner Schema Prefix also