Developer forum

Hi Aki,

If you're willing to use multiple paragraphs, one for each content type, this is very easy. Otherwise, currently it can be rather complex.

From the way you're describing, looks like you need to either have a custom IndexBuilder OR use the SQL Index builder using a very complex query to union all of the necessary data in a single result. Once you're there, is standard management of Repositories. 

Assuming you'll still be having separate searches for users, products and content, every time you change settings in one (i.e. add another field OR change boost values), you need to change the other one too.

Please consider that if you are using partial index builds (products and users), you'll have to subscribe to Product and User Save notifications to rebuild your custom index as well.

Hope this helps.

Nuno Aguiar

Hi Nuno,

Thanks for your input. I actually did it with a custom index like that in a previous project. But as you mention, the data collection can be a bit complex. 

But if the requirements are one single sortable search result list with everything mixed I guess its hard to do otherwise.

Regards / Aki.