\nThe display format of the column is set to ‘Display the entire path to the term in the field’.
\n
![\"Managed](\"https:\/\/www.itidea.nl\/wp-content\/uploads\/2012\/02\/MMDRefiner01.png\" "\\"Managed")
<\/a><\/p>\nA few documents are uploaded to the library and the metadata column is set to one of the terms. As can be seen, not the whole fieldvalue is displayed. That’s weird. How do I know which one to use if not the whole value can be seen? The whole value isn’t present as text to display in the panel! I was seriously surprised! But… hover over de terms and the whole path is displayed. But that’s not a satisfactory solution, the values have to be displayed properly!<\/p>\n Ok, I agree displaying the whole term tree path isn’t that useful in this case, but it’s needed somewhere else in the site, so the display format of the site column has to stay ‘Display the entire path to the term in the field’. The xslt of the refinementpanel can be adjusted to display the last term value now we know the tooltip does know the whole value.<\/p>\n Original xslt:<\/p>\n The new xslt looks a little bit different than that. If the fieldvalue contains less than 19 characters, no dots are displayed and the value can be used, but in that case the urltooltip is empty… To solve an empty tooltip, check out my next post<\/a>.<\/p>\n After the xslt has been implemented the refinementpanel looks like the picture below And the tooltip displays the whole term tree: SharePoint returns only the first 19 characters, so what happens when a term itself exists of 19 or more characters? On the one hand it’s great the 19 character limitation of displaying a whole termtree isn’t applied to this term, on the other hand, it doesn’t look very nice when the text continues outside the refinement panel.<\/p>\n The values of the refinement panel have a 19 character display limit. When displaying a whole termtree it’s likely this limitation will be exceeded. Just a few xslt adjustments are necessary to display the fieldvalues correct again.<\/p>\n","protected":false},"excerpt":{"rendered":" Search refiners can contain managed metadata fields to refine the results. Sometimes the display mode of the values look a bit weird in the refinement panel. Suppose a sitecolumn of a library is a managed metadata column bound to a … Read More »<\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[8],"tags":[42,34],"class_list":["post-1333","post","type-post","status-publish","format-standard","hentry","category-sharepoint-2010","tag-sharepoint-2010","tag-xslt"],"_links":{"self":[{"href":"https:\/\/www.itidea.nl\/index.php\/wp-json\/wp\/v2\/posts\/1333","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.itidea.nl\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.itidea.nl\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.itidea.nl\/index.php\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.itidea.nl\/index.php\/wp-json\/wp\/v2\/comments?post=1333"}],"version-history":[{"count":13,"href":"https:\/\/www.itidea.nl\/index.php\/wp-json\/wp\/v2\/posts\/1333\/revisions"}],"predecessor-version":[{"id":2042,"href":"https:\/\/www.itidea.nl\/index.php\/wp-json\/wp\/v2\/posts\/1333\/revisions\/2042"}],"wp:attachment":[{"href":"https:\/\/www.itidea.nl\/index.php\/wp-json\/wp\/v2\/media?parent=1333"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.itidea.nl\/index.php\/wp-json\/wp\/v2\/categories?post=1333"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.itidea.nl\/index.php\/wp-json\/wp\/v2\/tags?post=1333"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}
\nA full crawl is completed and the refinement panel shows the metadata refiner.
\nThe refinement panel now looks like this:
\n<\/a><\/p>\n
\nMaybe it’s a css issue or the left column of the screen isn’t wide enough? Starting up Firebug and checking out the value:
\n<\/a><\/p>\n
\nSharePoint returns only the first 19 characters and three dots…<\/p>\n
\nIt would be great to have on option to show only the last term value despite the column display format. An excellent configuration place would be an extra attribute in the filter categories definition xml.<\/p>\nDisplaying the last term value<\/h3>\n
\r\n <a href="{$SecureUrl}" title="{$RefineByHeading}: {$UrlTooltip}">\r\n <xsl:value-of select="Value"\/>\r\n <\/a>\r\n<\/pre>\n
\nFirst the fieldvalue has to be analyzed if it contains ‘:’. The ‘:’ means the value is a child term and the whole tree path is displayed.
\nFrom the value which contains the whole tree path the last term is filtered by a recursive xslt template \u00b4substring-after-last\u00b4.
\nThen a check has to be performed if the last term value contains the three dots. If it does, the last term value should be taken from the tooltip value, because the xslt Value doesn’t contain this value. Confusing, isn’t it?<\/p>\n\r\n<xsl:variable name="PartOfValue">\r\n <xsl:call-template name="substring-after-last">\r\n <xsl:with-param name="string" select="Value" \/>\r\n <xsl:with-param name="delimiter" select="':'" \/>\r\n <\/xsl:call-template>\r\n<\/xsl:variable>\r\n\r\n<xsl:variable name="PartOfTooltip">\r\n <xsl:call-template name="substring-after-last">\r\n <xsl:with-param name="string" select="$UrlTooltip" \/>\r\n <xsl:with-param name="delimiter" select="':'" \/>\r\n <\/xsl:call-template>\r\n<\/xsl:variable>\r\n\r\n<xsl:choose>\r\n <xsl:when test="($FilterCategoryType = 'Microsoft.Office.Server.Search.WebControls.TaxonomyFilterGenerator') and ($PartOfValue != '')">\r\n <xsl:if test="not(contains($PartOfValue, '\u2026'))">\r\n <xsl:value-of select="$PartOfValue"\/>\r\n <\/xsl:if>\r\n <xsl:if test="contains($PartOfValue, '\u2026')">\r\n <xsl:value-of select="$PartOfTooltip"\/>\r\n <\/xsl:if>\r\n <\/xsl:when>\r\n <xsl:otherwise>\r\n <xsl:value-of select="Value"\/>\r\n <\/xsl:otherwise>\r\n<\/xsl:choose>\r\n<\/pre>\n
\n<\/a><\/p>\n
\n<\/a><\/p>\n
\n<\/a><\/p>\nSummary<\/h3>\n