Hi,
quoting from the App Builder User's Guide:
About Auto-Discovered Facets
When you build a faceted seach page with either the Create Application Wizard and Create Page Wizard, you can select a table or view on which to build the page. If you create the page based on a table, the facets are auto-discovered using the Data Dictionary Cache. In contrast, if you build the page on a view or a SQL query, the facets are not auto-discovered. Instead, the wizard creates a facet region which only searches VARCHAR2 columns.
I'd like to know if besides the criteria explained above, APEX as of 23.2.6 makes any assumptions on the names of columns and any existing foreign keys ( and the state of these constraints by the way).
For instance I created a faceted search page based on a table containing several columns having FKs to their corresponding look-up tables and the wizard created automatically new LOVs where the return value matched the pk of the lool-up table which is always "ID" in my case and a description column whose name contained indeed “NAME”.
What I am not still completely clear with is if these assumptions are exclusively made basing on 1) the column name corresponding to a PK of the lookup table found via the FK in the data dictionary and the description column is assumed to be the first VARCHAR2 column in the lookup table or 2) if there are any other assumptions made to figure out which column is to be picked.
In contrast I created a second page based on a query and, as per the docs, nothing of the magic above happened, I had to add the LOVs manually and modify the facet configuration accordingly.
You understand that knowing in advance what the faceted search wizard expects to find can help a lot to build a page faster rather than having to create all these ancillary components manually.
Can someone of the team share some more info about this process?
Thank you
Flavio