The point is that Product Finder's questionnaires depends on parameters set in relevant menu items.
In fact, all important parameters such us thresholds, number of results, categories scope are set *only* in menu items.
This design choice allows for the very same questionnaire to be used on different sets of data.
Say that you have a questionnaire with "age class", "gender", "price range".
Simply by creating several menu items, you could use it "unchanged" to:
- filter 't-shirt' k2 items
- filter 'book' Joomla articles
- filter 'book' articles belonging to 'Thriller' category
...
Also, different content items (Joomla, K2) need different parameters and different views.
Hence Product Finder depends on menu items.
With that in mind you understand why reading a table and printing out a list of questionnaires doesn't quite cut it (we actually do that in the backend, btw).
So, the best workaround we can come up with is:
- create a dedicated menu comprised of Questionnaires menu items
- embed such menu into an article
