Forum Discussion
AlbertSP
May 03, 2023Copper Contributor
PnP Modern Search Filter - Managed Metadata fields display additional properties
The PnP Filter webpart uses the managed Property "RefinableString01" mapped to a "Fiscal Year" term set. There are additional properties being displayed that may seem confusing to end user and we wou...
DaveMehr365
May 04, 2023MVP
Hello AlbertSP
i do the same, here it looks fine:
I have a managed metadata column mapped to RefinableStringXXX:
Which version from pnp web parts do you have installed?
Best, Dave
- ADMEAMay 04, 2023Copper Contributor
DaveMehr365
Ver 4.3.0.0- ADMEAMay 04, 2023Copper Contributor
So its seems the issue stems from the Same Managed Metadata Property existing in different Content Types that are applied to different Libraries.
For ex: If Fiscal Year managed metadata column is part of Content Type ABC and is used in tagging files in Library ABC, the Filter looks OK.
However, if I add the Fiscal Year column to CT XYZ and Tag document in the XYZ library, the Filter choices seem weird. It Still works but it seems like there is an issue filtering multiple libraries in a site.
- DaveMehr365May 10, 2023MVP
Hello ADMEA
also with the same column in different content types, it's looks fine.
The newest version is 4.8.0: https://github.com/microsoft-search/pnp-modern-search/releases
I think it's a good idea, to update your version.
Best, Dave