Skip to Main Content

Java Development Tools

Announcement

For appeals, questions and feedback about Oracle Forums, please email oracle-forums-moderators_us@oracle.com. Technical questions should be asked in the appropriate category. Thank you!

Interested in getting your voice heard by members of the Developer Marketing team at Oracle? Check out this post for AppDev or this post for AI focus group information.

Caculated / Transiant attribute being set to null after filtering or sorting

Paul (MITsa)Feb 6 2025

JDeveloper 12c

Hi

We have the usual EO -> VO -> af:table set up.

In or VO we have a list of values which sets its own attribute and a secondary attribute (AttribNr) which doesn't need to be persisted.

AttribNr value is used in several other backing bean methods.

The value is set as a secondary return value from a list of values.

In the VO AttribNr is marked as "Calculated AttribNr'

When running our application AttribNr is set correctly but as soon as a filter is applied to the af:table AttribNr becomes null.

We have tried to create a transient EO attribute but the same problem occurs.

The only way to prevent AttribNr from being set to null after a filter is applied to the af:table is to mark the EO attribute as persistant, but then the auto generated EO insert/update query contains AttribNr in the field list but as AttribNr doesn't exist in the database table the query fails. (which is understandable)

How can we create a transient/calculated VO attribute which doesn't become null after a filter.

Thanks in advance
Paul

Comments

Processing

Post Details

Added on Feb 6 2025
2 comments
157 views