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!

View Object Attribute UI Format Hints and Table Filtering

MaximusDecimusOct 6 2025 — edited Oct 6 2025

Hi. I'm using JDeveloper 12.2.1.4. Our application has been upgraded from 11.1.2.4 (via 12c release 1).

As a matter of course in 11g, we defined the majority of numeric view object attributes with a UI Hint format, which made display of the relevant value simple in any table columns bound with the view object. However, where the table has a filter capability there is now a behavioural difference between 11g and 12c.

Where an operator is used in the filter field (e.g. “>”, “<” etc), the filter value is reformatted to the defined UI Hint format. For example, if I enter “>1000” in a numeric filter where the format is defined as “#,##0”, the filter value is reformatted to “1,000”. This is not the case in 11g. The underlying query result is correct, but the filter value displayed does not reflect what was queried.

I've read that table filtering has been redesigned in 12c but have not found any helpful Oracle documentation on the subject.

On the face of it, I am wondering what the benefit of using UI Hint Formats is in 12c where the attribute is going to be displayed in a (filterable) table? The formatting can also be achieved by defining a format in the table column (using a convertNumber component).

Is there a way to keep the UI Hint Formatting but make the table filter reflect the query criteria that were actually entered? I'd prefer not to be defining filter facets on all the application tables, and don't want to lose the operator capability in the filter columns.

Any help would be appreciated. Thanks.

Comments
Post Details
Added on Oct 6 2025
4 comments
79 views