Skip to Main Content
Feature Request FR-2535
Product Area Page Components
Status CLOSED

4 Voters

Faceted Search for other regions

rahime.tugrul Public
· May 23 2022

Idea Summary
Making Faceted Search available with other regions like Grid, Cards, Charts, Lists, Reflow Reports etc.

Use Case
The Standard Report is not the best choice for some Use Cases. But with Faceted Search only being able to work with them limits the capabilities of itself. Let's say you have a Chart Region where you also could use Faceted Search, which would make the filtering easier instead of recreating all those options on your own. Also, the simple Stuff, that you have with the interactive Grid/Report, like choosing which columns to show and downloading the data is not possible without a bigger workaround.

Preferred Solution (Optional)
Having in the Source-Drop Down in the Faceted Search expanded with the other regions that are available in APEX.

This idea has been closed due to the lack of community activity during the period since it was submitted.

Known Duplicates

Comments

Comments

  • zolo OP 3.3 years ago

    Cards is already there, there is a standalone search and filter in the Interactive Report and Grid so I don’t think it would be easy to mix the two. It could probably be used in Charts.

  • patrick wolf Admin OP 3.3 years ago

    Just for the record and for easier tracking, Faceted Search and Smart Filters are currently available for the following region types:

    • Classic Report
    • Cards
    • Map
    • Content Row Report
    • Table Data
    • plus all region type plug-ins supporting the new Supports Faceted Search / Smart Filters standard attributes flag
  • stew stryker OP 3.2 years ago

    I'm going out on a limb here to suggest Faceted Search support for IG and IR regions. 

    We just spent a bunch of time essentially creating this functionality manually because our (mostly older, non-technical, no disrespect to them) users struggle to use the standard IR/IG Actions→Filter or column filter options. That's especially true when they're searching ranges (BETWEEN 100 and 2500).

    I know this would be difficult to implement, but the need is there.