Quick question: Should we expect the following configuration to work?
- Faceted Search Region
- Facets
- P22_SEARCH
- Search Type: Row Search
- Source / Database Column(s): <blank>|query column alias|generic report column name
- Classic Report Region
- Region Source Type: PL/SQL Function Body returning SQL Query
- Projection has 12 fixed columns and up to 50 dynamic columns
- Use Generic Column Names: Yes
Online help for Row Search facet Database Column(s) property says:
- Row Search: Enter a comma delimited list of case sensitive database column names of type VARCHAR2 used for text search. If no column is specified, all VARCHAR2 columns will automatically be used.
However, both leaving it blank (the behaviour thus described in the help is desirable), or specifying a database column name from the query (CLIENT_ID)/the corresponding generic column name from the region columns (COL10) result in an error:
No search columns have been provided for facet P8022_SEARCH
Technical Info (only available for developers)
- is_internal_error: true
- apex_error_code: APEX.FS.NO_SEARCH_COLUMNS_PROVIDED
- component.type: APEX_APPLICATION_PAGE_REGIONS
- component.id: 62880737192951794
- component.name: Search
- error_backtrace:----- PL/SQL Call Stack ----- object line object handle number name 0x4b2735ea0 1055 package body APEX_240200.WWV_FLOW_ERROR.INTERNAL_GET_ERROR 0x4b2735ea0 1124 package body APEX_240200.WWV_FLOW_ERROR.INTERNAL_ADD_ERROR 0x4b2735ea0 1608 package body APEX_240200.WWV_FLOW_ERROR.RAISE_INTERNAL_ERROR 0x33fd48938 3626 package body APEX_240200.WWV_FLOW_FACETED_SEARCH.GET_FR_ATTRIBUTES 0x33fd48938 4262 package body APEX_240200.WWV_FLOW_FACETED_SEARCH.RENDER 0x684f5db58 2701 package body APEX_240200.WWV_FLOW_REGION_NATIVE.RENDER_REGION 0x649bb74a8 3710 package body APEX_240200.WWV_FLOW_PLUGIN.RENDER_REGION 0x649b7ed98 1118 package body APEX_240200.WWV_FLOW_DISP_PAGE_PLUGS.DISPLAY_REGION_BODY 0x649b7ed98 1636 package body APEX_240200.WWV_FLOW_DISP_PAGE_PLUGS.RENDER_REGION 0x4de8cb320 1912 package body APEX_240200.WWV_FLOW_PAGE.RENDER_COMPONENTS 0x4de8cb320 2005 package body APEX_240200.WWV_FLOW_PAGE.RENDER_PAGE_SLOT 0x4de8cb320 3014 package body APEX_240200.WWV_FLOW_PAGE.EMIT_BODY 0x4de8cb320 3262 package body APEX_240200.WWV_FLOW_PAGE.RENDER 0x6da0690b8 3393 package body APEX_240200.WWV_FLOW.SHOW 0x6da0690b8 5542 package body APEX_240200.WWV_FLOW.RESOLVE_FRIENDLY_URL 0x6da0690b8 5606 package body APEX_240200.WWV_FLOW.ROUTE_FRIENDLY_URL 0x138de928f8 6 anonymous block
I'm assuming the faceted search is struggling with the highly dynamic nature of the report source and column projection?
APEX 24.2
Oracle AI Database 26ai Enterprise Edition Release 23.26.1.1.0 - for Oracle Cloud and Engineered Systems