Hi,
JDeveloper/ADF 12.2.1.4.0, Build JDEVADF_PT.12.2.1.4.0_GENERIC_190911.2248.S.
Application migrated from 11.1.9.0.
I have a page with 1 table on it. This table contains 19 columns.
For each of these columns, we want a filter to be present. For most of them this works fine OOTB, except for 2 of them.
When setting the property filterable="true" on the column, it does not shown an input field in the filter section for those 2 columns.
When adding manually a filter facet, including an input field or a selection, after selecting an option, the table is refreshed but did not take into account this filter. When showing the query being launched, with the other columns we see the extra query condition being added, but for those 2 columns we do not see any query condition being added.
Here is the definition of 1 of these columns in the view object:
<ViewAttribute
Name="Recipient"
IsUpdateable="false"
IsPersistent="false"
PrecisionRule="true"
Precision="40"
Type="java.lang.String"
ColumnType="VARCHAR2"
AliasName="RECIPIENT"
Expression="RECIPIENT"
SQLType="VARCHAR"
LOVName="LOV_Recipient">
<DesignTime>
<Attr Name="_DisplaySize" Value="40"/>
</DesignTime>
<Properties>
<SchemaBasedProperties>
<LABEL
ResId="be.fgov.health.mediflow.medicalcosts.model.entities.Envelope.Recipient_LABEL"/>
<CONTROLTYPE
Value="choice"/>
</SchemaBasedProperties>
</Properties>
</ViewAttribute>
Here is the column definition from the table :
<af:column headerText="#{bindings.EnvelopeWithInvoicesView.hints.Recipient.label}"
id="c5" sortable="true" filterable="true"
sortProperty="Recipient">
<af:selectOneChoice value="#{row.bindings.Recipient.inputValue}"
label="#{row.bindings.Recipient.label}"
required="#{bindings.EnvelopeWithInvoicesView.hints.Recipient.mandatory}"
shortDesc="#{bindings.EnvelopeWithInvoicesView.hints.Recipient.tooltip}"
id="soc3" readOnly="true">
<f:selectItems value="#{row.bindings.Recipient.items}" id="si3"/>
</af:selectOneChoice>
<f:facet name="filter">
<af:selectOneChoice label="Label 1" id="soc7"
value="#{vs.filterCriteria.Recipient}" autoSubmit="true">
<f:selectItem id="si9" itemValue="" itemLabel="" />
<f:selectItem id="si12"
itemLabel="#{msgGeneral.BENEFICIARY_PERSON}"
itemValue="VICTIM"/>
<f:selectItem id="si10"
itemLabel="#{msgGeneral.BENEFICIARY_PROVIDER}"
itemValue="PROVIDER"/>
<f:selectItem id="si11"
itemLabel="#{msgGeneral.BENEFICIARY_OTHER}"
itemValue="OTHER"/>
</af:selectOneChoice>
</f:facet>
</af:column>
I compaired this attribute with another one that did work with the filtering, but didn't find any difference.
I also tried it programmatically, following the blog of Arik Lalo : programmatically-filter-an-adf-table, including the remark of Dimitar. Did not work. I used this method to find out the possible queryable fields and in this list my “Recipient” attribute was included. Presuming that the ADF BC part was correctly configured.
Why does the filter on my Recipient column does not add an extra query condition on my view object query?
Any help is more then welcome.
Kind regards.
Filip Huysmans