Search problem in all workspaces

[PLM-Sylvain.Bailly]

Hello,

The search function acts strangely. When I try to find something in ALL the workspaces, I have NO result. But when I try to do the same search in a specific WS where I know that the result must not be empty, I have a result. I think that the search function use a script and when I check all the workspaces, the search exceeds the 9 seconds (timeout) that’s why I have anything.

If I’m right, is it possible to change these 9 seconds (in 20 seconds for example) somewhere in the configuration?

Thank you for your help,

Sylvain

[dvirh]

Hi Sylvain,

Thanks for reaching out on this issue! There is a known issue with Search that we are currently working on that when there are too many results for the search criteria, the message to the end user makes it sound like no results were found. We are working to change that message to the user to make it clearer. Can you please help verify that this is your issue by further constraining the search criteria to see that you are getting search results when the criteria is constraint enough? The threshold at this point is 500 results. Meaning that is the search criteria returns more than 500 results, he user is notified that no results have been found.

[PLM-Sylvain.Bailly]

Hi Hagay,

There are less than 500 results in all the WorkSpaces (maximum 200). For information we have around 30 WS.

When I search for example "copper", it seems that it searches in priority in the WS where there are only few data and do in last the most important WS (from the data size). Is it possible to increase these 9 seconds?

Cheers,

Sylvain

[dvirh · Accepted solution]

Hi Sylvian,

The search is performed in a separate search index and not in the workspaces themselves. There is no WS priority to the search. There is also no reason for any scripts to execute during search and script timeout cannot have any impact on search performance as far as I can tell. Given that you have confirmed that there should not be more than 500 search results, the issue might be with the search index itself. I will ask customer support to contact you so that we can re-index your tenant and see if that resolves your issue.