Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Modern Search: Many Refiner WebPart's for single Search Results webpart #341

Open
1 of 2 tasks
ervingayle opened this issue Oct 31, 2019 · 1 comment
Open
1 of 2 tasks

Comments

@ervingayle
Copy link

Category

  • Question
  • Bug
  • [] Enhancement

Expected or Desired Behavior

We have a use case where we would like to show one instance of the refiners webpart depending on mobile vs desktop views on a page. There may be other ways to do this and potentially maintaining state between more than one instance of a refinement set may be tricky but is this possible?

Observed Behavior

Add a second search refiners webpart, this webpart will display the existing search results webpart instance but the search results webpart itself only lists one instance of the refiners webpart(s) listing

Steps to Reproduce

Using a modern communications site in SP Online:
Add Modern Search: search results webpart to a page
Add Modern Search: refiners web part on a page
Connect the Search results web-part to the existing search refiners webpart
Add a second search refiners webpart, this webpart will display the existing search results webpart instance but the search results webpart itself only lists one instance of the refiners webpart(s) listing

@FranckyC
Copy link
Member

Hi @ervingayle unfortunately this scenario isn't supported. You can't plug multiple refiners to a single search results. Why not adding a second search results WP with the same config and hide it the same way you do for the refiner in mobile view? Actually, how do you hide it, I'm curious ;)?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants