Developer forum

You can create your own custom SQL queries:

Your customer is wrong and you should recommend them to do something else.

A combined search experience does not require a single shared index. What the customer needs is unified results in the UI — not necessarily merged data in one repository.

Recommended approach

• Keep products and content in separate indexes.

• Use a unified query layer to search both simultaneously.

  • One page, 2 paragraphs, 2 apps - product catalog and query publisher, maybe in 2 tabs if they like things old fashioned.

• Control ranking per entity type (e.g., prioritize products for commercial queries).

• Present results in clearly grouped sections (e.g., Products, Articles).

• Apply filters primarily to products, avoiding cross-type facet confusion.

This approach provides better relevance control, clearer UX, and more flexibility long term, while still delivering a seamless combined search experience.

Hi,

Thanks for the input. Unfortunately we don't have much we can say about the designs their agancy has delivered. At the moment the search is the standard Swift2 way. Which I am happy with. :)  

Thay don't have many product so the facetting for products would be "Products" in this case.

But I understand from your answer that currently it is not possible to create custom indexes?

Regards / Aki 

It is possible to make custom indexes. Using SQL

OK. But not the "DW9" way by code?

Maybe that part of the documentaion is old. (Or maybe I was unclear)

Found this:

https://doc.dynamicweb.dev/documentation/extending/indexing/indexes.html#creating-a-custom-indexbuilder

And then tried to create i simple custom index and it worked fine. 

Regards / Aki 

Haha, yes, I see that now, that it was about SQL Indexes. I did some "selective reading". :)

Mvh / Aki