Closed JoeAyre closed 1 week ago
Further to this, I have also attempted using a for a tenant level term set and I still don't get any results in the 'Data Visualization' web part. I'm sure I have everything set up correctly so not sure why the taxonomy picker filter is not working.
Just to close this issue out, it seems that there was another part of key information from this issue I linked to in the opening post of this issue.
_You should map the OWS_TAXID_DOCSCOPE from your search schema rather than OWSDOCSCOPE
Now that I have mappped the owstaxid
One thing to note, I have got this working for both a tenant level term set AND a site collection level term set, on the same page, in the same filters web part, so I'm not sure if the advice Ensure your TermSet is Tenant Level (not site collection) is still accurate. Just thought I'd add that in case it helps someone trying to do the same thing.
Thanks, Joe
Hi @JoeAyre,
Thank you for your feedback and your investigations. Yes, in all of our documentation about the taxonomy, if you want a unique filter result and profit multilingual filter, we highly recommend you to use owstaxid[property] - it is a best practice. With the latest version, the Tenant Level Only is not relevant anymore, we added the capability to get the TermSets from the Site Collection too.
Thanks 🙏🏻
Hi Aequos team,
I'm hitting the same problem as the original poster of this issue i.e., getting no results when picking a term from a taxonomy picker.
I notice n the issue I linked to above that the following was mentioned:
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