Developer forum

You would probably want to use conditions in "Data Lists" instead.
You can create a list that gets data from the given table. Then create a condition on that list in which you specify, that the criteria part of the condition should come from Request (you can use the Helper/Magic wand).

Now the list only shows data that corresponds to that criteria.

Well - you can do a small add-in that does the trick.

Attached a notification subscriber that will make global template tags for all templates.

Copy the dll to /Bin and in every template you can now write "<!--@SessionTags-->" and that will give you a list of available template tags containing the sesion vars...

So it would give a list like:
<!--@Session-SessionStatDone-->:True
<!--@Session-DW_Statv2Session_Statv2SessionID-->:675

So for each session var you would have a template tag called
Session-NameOfSessionVar.

Wrong thread... sorry!

Hi Jeppe,

Thanks for that. However, that allows us to search using the nodule itself. However, the question was more about *integration* standard search with data management. E.g. combine search results, just like you can do it with pages, paragraphs, News etc....

Imar

Hi Imar

Im afraid there is no way of extending the search module in the way of combining the results from the search module with the results from a custom search (using DataLists, custom code or something else).

As Jeppe suggests, I think the easiest way to get around this issue is to implement a custom search that searches all the data you need to search in.

 - Lasse

If you just want to search a single view you can install a bogus module and register search properties for this. Just yesterday I uploaded an article where I use this approach to search in ForumV2 on Engage: http://engage.dynamicweb-cms.com/default.aspx?id=361&articleid=223. Peter Terkildsen once wrote an article on integrating search in custom modules. I'm pretty sure that you know this one, Imar, but others may not, so here it is:) http://engage.dynamicweb-cms.com/default.aspx?id=361&articleid=122.

Using this approach does the trick perfectly, but if you have many Data lists you want to search, it may at some point become difficult to manage with many custom module registrations that doesn't do anything besides search.