I try to configure search navigation and User Current Query from drop down always say target not found. I try to change to search results web part ,but it is not working. It set back to target not found.

Hi,

According to your description, my understanding is that you cannot change the User Current Query from in the Search Navigation web part.

I recommend to delete all the search result web parts in the result page and then add a new search result web part, then change the User Current Query from in the Search Navigation web part.

Best regards.

Thanks

I have the exact same problem...

I have a search results page where I added a custom Search Results webpart. This webpart was created by exporting the out of the box Search Results. In the exported copy, I have set the TrimDuplicates to false and imported this customized Search Results into the webpart gallery. Then I added the custom search results to the results page and removed the out of the box webpart.

When I check the refiner webpart and the searhbox webpart, they are both connected to the custom search result webpart. However, the Search Navigation webpart displays "target not found" as the selected value in the "use current query from" dropdown.

When I change this to my search results and press the "Apply" button, it changes back to target not found. The same happens when I click OK.

So, I tried to add a default search results to the page again and without any change, the search navigation sets THAT webpart as selected. When I change it to my custom webpart and press apply, it changes back to the out of the box one.

Oh, the search results webpart works by itself. It's like the search navigation does not accept anything but the default search results.

 

OK, I found a solution for this.

When you export the search navigation webpart, the webpart contains a property "QueryGroupName" with the value "Default".

<property name="QueryGroupName" type="string">Default</property>

When you export the search results webpart, there's a property "DataProviderJSON" where you will find the same "QueryGroupName" key. In my exported version of the search results, the value of this QueryGroupName was a GUID. So, I changed it to "Default" and uploaded it again.

I added it to my search results page and now it works. The search navigation webpart selects the search results webpart by default and doesn't reset to "target not found".

Don't know why this was a GUID in my instance. I retried it with a default search results webpart and the GUID wasn't there. It was "Default" from the beginning.

OK, I found a solution for this.

When you export the search navigation webpart, the webpart contains a property "QueryGroupName" with the value "Default".

<property name="QueryGroupName" type="string">Default</property>

When you export the search results webpart, there's a property "DataProviderJSON" where you will find the same "QueryGroupName" key. In my exported version of the search results, the value of this QueryGroupName was a GUID. So, I changed it to "Default" and uploaded it again.

I added it to my search results page and now it works. The search navigation webpart selects the search results webpart by default and doesn't reset to "target not found".

Don't know why this was a GUID in my instance. I retried it with a default search results webpart and the GUID wasn't there. It was "Default" from the beginning.

Hello Everybody,

I had the same situation and in my case the solution was very simple.

Seems that the default aspx page was corrupted (results.aspx).

I created a new one from Search Center -> Site Contents -> Pages -> New Page.

Replaced the corrupted results.aspx with the created AllResults.aspx page in Site Settings -> Search Settings -> Configure Search Navigation.

The Search is working properly now!

Hope this information can help!