Developer forum

Forum » Dynamicweb 10 » UI Product search on Global custom field

UI Product search on Global custom field

Davy Capiau
Reply

Hi,

Is it possible to configure something in DW10 to search in a specific Global custom field?

Case: we have a 'secondary ID' we want to search on.

 


Replies

 
Jeppe Eriksson Agger Dynamicweb Employee
Jeppe Eriksson Agger
Reply
This post has been marked as an answer

Hi Davy,

With the standard UI queries being used, it's currently not possible to do. You could create your own UI queries and inject new nodes into the tree. Let me know if you want to know more about this approach.

We have internal discussions about if and how it should be possible to configure, but we don't have any conclusions yet.

- Jeppe

Votes for this answer: 1
 
Nicolai Pedersen Dynamicweb Employee
Nicolai Pedersen
Reply

You can create a query:

https://doc.dynamicweb.dev/manual/dynamicweb10/products/queries.html

 
Davy Capiau
Reply

Hi guys,

Thanks for the feedback. Where do you link the query to the backend search function?

 
Michael Knudsen
Reply

Shouldn't it be possible by using the "Search field" as decribed in the documentation?

https://doc.dynamicweb.dev/manual/dynamicweb10/settings/areas/products/advanced/general.html

Br. Michael Knudsen

 
Jeppe Eriksson Agger Dynamicweb Employee
Jeppe Eriksson Agger
Reply

Hi all,

Since there are two different query concepts in play here, let me just clear up some confusion that may play a roll. UI queries are implementation that derive from the Dynamicweb.CoreUI.Data.DataQueryBase class. These are used throughout the UI to provide data to screens. They are also available through the Management API. In contrast, index queries -- the ones used in My queries and Shared queries (and referenced by Nicolai) -- are definition files that use an index in a repository to search in a Lucene index based using manually defined expressions.

Search on a list screen uses a UI query so it's not possible to link an index query to the search field. If you create your own UI query and tree node to use that query, the list screen will use that query to search and you can fully control where and how the search is performed.

@Michael, what specifically are you referring to? The documentation states that the search field is used in product selector search, i.e., from a product selector UI component. It's not intended to be used in lists.

Again, we are looking into ways of making this better, but we don't have a solution for it just yet.

- Jeppe

 
Michael Knudsen
Reply

@Jeppe, maybe the documentation/ UI should be more specific since it only states "product selector search". I was thought this was the search field in backend.

Where are the "product selector UI component" used in the backend?

Br. Michael Knudsen

 
Michael Knudsen
Reply

DW10.14.0 should have this feature "Products - Database search - Definiable which attributes to search in"
https://doc.dynamicweb.dev/documentation/fundamentals/dw10release/releasenotes/workiteminfo.html?workitemid=23120

 
Jeppe Eriksson Agger Dynamicweb Employee
Jeppe Eriksson Agger
Reply

The product selector is used many places in the backend. Whenever you need to select a product, the product selector allows you to do that. One example is when you attach a product to a group. The search field is powered by the default index and using the freetext search field you define.

The user story that you link to does indeed allow you to specify which database field you want to include in search. One issue is that it's still in code review, so I cannot guarantee that it will make it into 10.14. Another issue is that it only supports certain product lists, specifically the ones using database lookup. That means that lists under My queries and Shared queries for example are not included in this. Finally, it only supports standard fields and custom fields. Category fields are not supported. That does cover the initial request, but due to these reasons I do not view this as a solution -- at least not a complete solution. So, I probably should have been clearer in my answer: We do not have a complete solution for this issue, but a partial solution is coming within the next couple of releases :)

- Jeppe

 

You must be logged in to post in the forum