Skip to Main Content
Feature Request FR-2224
Product Area Page Components
Status ROADMAP

19 Voters

Allow searching HTML Expression columns in Interactive grid

evelina.karolyi Internal · Dec 1 2021

Idea Summary
This is similar but not the same as FR-2029. 

I am proposing extending Search to HTML Expression type of columns. 

Use Case
I often HTML Expression to add some custom formatting or tooltip to some lengthy columns (where the column source data is text). Ex: <div title="&COLUMN_NAME.">&COLUMN_NAME.</div>

Current functionality makes it impossible to search in these columns, whereas it is even more relevant (at least in my use cases) to be able to search in these, consider besides fixed row height most of the times only fraction of the content is really visible. As a workaround I am adding an extra text column against the same source column that I exclude from the displayed columns list, just so that it can be searched. This obviously is an overhead, especially as we are working with numerous such data columns (within the same grid) and is making it confusing to select among columns with similar names (when we want to tailor the report from the UI )

Preferred Solution (Optional)
I'd just allow searching the HTML Expression type of columns, just like any other text

This is currently on the roadmap for a future release of Oracle APEX.

Comments

Comments

  • john.snyders APEX Team OP 3.6 years ago

    I think using the column advanced config option cellTemplate would be a simpler workaround. Rather than for example HTML Expression leave the type as Text Field and enter this in Advanced JavaScript Initialization Code.

    function(config) {
    config.defaultGridColumnOptions = {
        cellTemplate: "<span>&ENAME.</span>"
    }
    return config;
}

    We already have an internal ticket for this enhancement.

  • evelina.karolyi OP 3.6 years ago

    Thanks for the hint John! 

    I'll use your suggestion in the mean time

    kind regards

    Evelina

  • nicolas pilot OP 3.4 years ago

    BIG Vote for this idea. 

    The filter should be enabled for HTML Expression and use the “Database Column” to do the search and not the “HTML Expression”.

    Same think for the Download (CSV/Excel), the value should be the value of the “Database Column” and not the “HTML Expression”.