Timeline for Is there a way to have a single Metadata Navigation which work on multiple documents libraries which share the same site columns
Current License: CC BY-SA 4.0
12 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Nov 13, 2019 at 12:57 | comment | added | Ganesh Sanap - MVP | Sure, try it and let me know if this works for you or if you face any issues. | |
| Nov 13, 2019 at 12:48 | comment | added | John John | ok thanks for the clarifications, will try your appraoch and let you know the results.. sorry i do not have enough reputation to rate your reply and you useful comments.. thanks | |
| Nov 13, 2019 at 12:42 | comment | added | Ganesh Sanap - MVP | In order to use classic page on your communication site, try adding Web Part page Content type on Site Pages library. And add a search refinement panel in the search results means you need to create one classic page where you will add Search Results web part and you need to edit that page in order to add refinement panel. You don't have to edit the osssearchresults.aspx page. | |
| Nov 13, 2019 at 12:34 | comment | added | John John | The issue is that i am working on modern communication site and on a modern team site, and i am unable to create classic page, all the pages i can create will be modern pages, so i am not sure if i can add a classic refiner web part into modern teams or modern communication sites? second question, in one of the links you provided they mentioned the following add a search refinement panel in the search results page but the search page (osssearchresults.aspx) can not be edited.. so i am a bit confused,, | |
| Nov 13, 2019 at 12:18 | comment | added | Ganesh Sanap - MVP | Yes, you are right. You need to use classic UI for this. | |
| Nov 13, 2019 at 11:56 | comment | added | John John | wonderful your update is exactly what i am looking for! but one last question, if i follow this appraoch then i have to stay on classic UI ? is this correct? as i do not think the modern search will allow us to define our custom refiners as in the classic search ? | |
| Nov 13, 2019 at 11:11 | comment | added | Ganesh Sanap - MVP | Check update section in answer to check how to create refiners using managed metadata. | |
| Nov 13, 2019 at 11:11 | history | edited | Ganesh Sanap - MVP | CC BY-SA 4.0 | added 503 characters in body |
| Nov 13, 2019 at 10:46 | comment | added | John John | ok i got your point, but can i link the refiner with the term sets' terms? or i have to manually manage the refiners? | |
| Nov 13, 2019 at 10:23 | comment | added | Ganesh Sanap - MVP | No, user will not have to search for values in search box. Search box is optional... You can add refiners like the metadata navigation only. So, this is the only option you can filter the documents from multiple libraries. Using metadata navigation and fetching documents from multiple libraries is not possible. | |
| Nov 13, 2019 at 9:58 | comment | added | John John | ok thanks for this, but when i define Metadata Navigation on the list, the filters will be connected to the term sets, while using the search web parts appraoch the user will have to type-in the filter values, rather than selecting the related terms... so that why i was asking if we can have the same user experience for the Metadata navigation but to filter multiple document libraries.. | |
| Nov 13, 2019 at 7:47 | history | answered | Ganesh Sanap - MVP | CC BY-SA 4.0 |