One more Standard table filter weird work

Question

In the same VO described in previous thread: Standard table filter weird work
I have another filter trouble.
The attribute is calculated, not bound to entity.
SQL:to_char(case when ID_BASE_TYPES_MIME is null then substr(THE_VALUE, 0, 100)
            when ID_BASE_TYPES_MIME = 7 then
       dbms_lob.substr(
          regexp_replace(LargeTextData.DATA_TEXT, '<.*?>|&.*;')
          , 100)
            else LargeBinaryData.Filename
       end) as CONTENT_PREVIEW,VO attribute:<ViewAttribute
    Name="ContentPreview"
    IsUpdateable="false"
    IsPersistent="false"
    PrecisionRule="true"
    Precision="255"
    Type="java.lang.String"
    ColumnType="VARCHAR2"
    AliasName="CONTENT_PREVIEW"
    Expression="CONTENT_PREVIEW"
    SQLType="VARCHAR">
    <Properties>
      <SchemaBasedProperties>
        <LABEL
          ResId="ru.miit.cms.model.view.ContentComplexView.ContentPreview_LABEL"/>
        <DISPLAYWIDTH
          Value="90"/>
      </SchemaBasedProperties>
    </Properties>
  </ViewAttribute>With logging turned on I apply filter like P or \P\* - anything that contains letter P. ADF table with standard filter shows me no rows.
I take the executed SQL and parameter value from AdminServer-diagnostic-1.log. It is like:SELECT * FROM ( main query ) QRSLT  WHERE ( ( (CONTENT_PREVIEW LIKE ( :vc_temp_1 || '%') ) ) )
[SRC_CLASS: oracle.jbo.server.OracleSQLBuilderImpl] [APP: CMS] [SRC_METHOD: bindParamValue]  [850] Binding param "vc_temp_1": %РI execute this query in PL SQL Developer and it shows me 2 records - that is correct.
While ADF shows me no records, executing the same VO with the same parameters - that is wrong.
From this SQL query I also created a test VO with vc_temp_1 bind variable = %Р and run it in AppModule Tester. It shows me 2 rows.
Any ideas?
JDev 11.1.2.2

Answer 1

Hello Derio,
Thanks for your attention. This view object is a part of a composite application with lots of business components, running ~stable on 11.1.2.2. Sherman installed, of cause.
There are several tables with filters and all of them work fine except this attribute in this VO.
I believe the filter would work with no problems with such attribute if I create a clean new application, but in my specific case it doesn't.
The trouble is I don't know where to look for the error source because generated SQL and app module tester seem fine.