Skip to main content

ADF Exact custom filters

Step 1)
Add your custom filter to the column filter facet.
  <f:facet name="filter">
    <af:selectBooleanCheckbox value="#{backingBean.customfilter}"         id="id99"/>
  </f:facet>

Step 2) Create the getters and setters in your backing bean
    public Boolean getCustomfilter(){
        Boolean returnobj = null;
        Object filterValue = super.getFilterValue("AttributeName");
        if (filterValue != null){
            returnobj = ("Y".equalsIgnoreCase(filterValue.toString())) ? Boolean.TRUE : Boolean.FALSE;
        }
        return returnobj;
    }
 
    public void setCustomfilter(Boolean deletefilter){
        String value = filter == null ? null : (deletefilter) ? "Y" : "N";
        super.setFilterValue(value, "AttributeName");
    }

NOTE: Dates

Filtered Dates with timestamps in ADF dont work very nicely if you just want to filter by date. So your can modify the date filters as above and here is some code to help with the process. (Note you will need to override the queryListener)
just call this from your listener.

ArrayList fieldNames = new ArrayList();
fieldNames.add("DateAttr");
queryWithDateFilter(
queryEvent, vo, "#{bindings.CustomVOQuery.processQuery}", fieldNames);


public void queryWithDateFilter(
  QueryEvent queryEvent, ViewObject vo, 
  String mappedQueryEL, List fieldNames){

  FilterableQueryDescriptor fqd = 
    (FilterableQueryDescriptor)queryEvent.getDescriptor();
  Map map = fqd.getFilterCriteria();

  if (fieldNames != null){
    Map selectedValues = getSelectedValues(fieldNames, map);
    StringBuilder whereClauseSql = new StringBuilder();
    for (String fieldKey : fieldNames){
      String filterKey = "dateFilter_" + fieldKey;
      Object selectedValue = selectedValues.get(fieldKey);
      if (selectedValue != null){
        fqd.getFilterCriteria().put(fieldKey, null);
        AttributeDef def = getAttributeDefForKeyName(vo, fieldKey);
        whereClauseSql.append(
          "TRUNC(" + def.getColumnNameForQuery() + ", 'DDD') = :" + filterKey);
        vo.defineNamedWhereClauseParam(filterKey, convertDate(selectedValue), null);
        vo.ensureVariableManager().setVariableValue(
          filterKey, convertDate(selectedValue));
      } else {
        if (hasParam(filterKey, vo.getNamedWhereClauseParams())){
        vo.removeNamedWhereClauseParam(filterKey);
      }
     }
   }
   if (whereClauseSql.length() > 0){
     vo.setWhereClause(whereClauseSql.toString());
    } else {
      vo.setWhereClause(whereClause);
    }
    JSFUtils.invokeMethodExpression(
      mappedQueryEL, Object.class, QueryEvent.class, queryEvent);
    for (String fieldKey : fieldNames){
      Object selectedValue = selectedValues.get(fieldKey);
      fqd.getFilterCriteria().put(fieldKey, selectedValue);
    }
  } else {
    JSFUtils.invokeMethodExpression(
      mappedQueryEL, Object.class, QueryEvent.class, queryEvent);
  }
}

protected Map getSelectedValues(
  List fieldNames, Map mapValues){
  Map returnMap = new HashMap();
  Set set = mapValues.keySet();
  for (String key : set){
    if (fieldNames.contains(key)){
      returnMap.put(key, mapValues.get(key));
    }
  }
  return returnMap;
}

private Object convertDate(Object selectedValue){
   if (selectedValue != null && selectedValue instanceof java.util.Date){
     java.util.Date dateValue = (java.util.Date)selectedValue;
     return new Date(new java.sql.Date(dateValue.getTime()));
   } else {
    return selectedValue;
  }
}

protected AttributeDef getAttributeDefForKeyName(
  ViewObject vo, String fieldKey){
  AttributeDef def = null;
  AttributeDef[] defs = vo.getAttributeDefs();
  if (defs != null){
    for (AttributeDef currentDef : defs){
      if (currentDef.getName().equalsIgnoreCase(fieldKey)){
        return currentDef;
      }
    }
  }
  return def;
}

Comments

Popular posts from this blog

ADF sort of generic screen for tables with the same structure

We have a couple (about a hundred) of tables with the same structure (Code, Description, Create Date, Update Date). So I wanted to do something simple so that I did not have to create all these screens 1) EO   I created the EO based on one of the tables I had that had the above columns. I then Added a transient attribute called table name to my EO based on a groovy expression. (the expression needs to change as I am reading web tier stuff from the model layer but I will fix this later) I then generated a java class for my EO. And added the following overriden method to my newly created java class. protected StringBuffer buildDMLStatement(int i, AttributeDefImpl[] attributeDefImpl,   AttributeDefImpl[] attributeDefImpl2, AttributeDefImpl[] attributeDefImpl3, boolean b) {   StringBuffer statement = super.buildDMLStatement(   i, attributeDefImpl, attributeDefImpl2, attributeDefImpl3, b); return new StringBuffer(StringUtils.replace(statement.to...

MANIFEST.MF merge JDeveloper for an executable jar

Goto your project > properties. Then click on deployment in the menu. Edit or add a jar deployment profile. Fill in the details under jar options (select Include manifest and give it a main class name) Also remember that the merge functionality only works with a BLANK line at the end of the merge file. REALLY this caught me. My merge file contents: Class-Path: commons-codec-1.3.jar [...empty line here CRLF...]

ADF: LOV Description instead of code

I keep on forgetting how to do this so this is a note to self in terms I understand (ie pictures): Add the related entiy object to yours (in the example we are adding RegionEO(list of values) to CountryEO) Now add the RegionName field from the EO and a transient attribute (I named mine RegionNameLOV) Make the transient attribute updateable and base it on the expression RegionName (the description you wish to display) Add a list of values to RegionNameLOV and map BOTH key to parent fk (region id here) AND RegionName to your transient coulmn (RegionNameLOV).  Map the transient as an Input text with List of Values. Then just drag the lov item onto the page (RegionNameLOV)