search

aequos-solutions / modern-data-visualizer

Documentation for the Modern Data Visualizer solution
https://aequos-solutions.github.io/modern-data-visualizer/
8 stars 7 forks source link

[BUG] Taxonomy Filter does not filter the documents -> no results #67

Closed satoali17 closed 1 year ago

satoali17 commented 1 year ago

Version used Ex: 1.4.1.0

Describe the bug After filtering for taxonomy term no documents are displayed although documents has the same taxonomy term.

To Reproduce Steps to reproduce the behavior:

  1. create taxonomy termset Scope
  2. create multiple terms inside termset scope
  3. create custom taxonomy column DocScope
  4. add some documents and assign a term of termset Scope
  5. Set RefinableString01 to crawled property OWS_DOCSCOPE
  6. configure search filter web part -> filterfield = RefinableString01 & Template = Taxonomy Picker
  7. search for documents
  8. select the taxonomy term
  9. see described error

Expected behavior Only show document assigned to the chosen taxonomy term.

Screenshots

Desktop (please complete the following information):

Additional context When you need more details, please feel free to contact us. Thanks

Laul0 commented 1 year ago

Hi @satoali17,

We think that your environment could not works with managed metadata with the current configuration.

  1. Please read the documentation about the Managed Metadate Filter: https://aequos-solutions.github.io/modern-data-visualizer/usage/data-filters/#taxonomy-picker-configuration
  2. Ensure your TermSet is Tenant Level (not site collection)
  3. You should map the OWS_TAXID_DOCSCOPE from your search schema rather than OWS_DOCSCOPE
  4. Ensure your library and site are well reindexed (Microsoft met some trouble lately with the search engine)

Hoping this information will help you.

Best

satoali17 commented 1 year ago

Hello Laul0, thanks for your quick response. We tried the step three and it works fine for us.

JoeAyre commented 3 weeks ago

Hi @Laul0 , I'm hitting the same problem as the original poster of this issue i.e., getting no results. I notice that you mention the following:

Ensure your TermSet is Tenant Level (not site collection)

Is this a requirement? We have site collection level term sets that we wish to use via the taxonomy picker but reading the above suggests this is not possible. Can you confirm this please? Thanks, Joe

Laul0 commented 2 weeks ago

Hi @JoeAyre,

Thank you for your question. No, since the latest version, you can select Site Collection TermSet.

Enjoy it :)