Home > SharePoint, SharePoint 2010 > SharePoint 2010 Bug: Search Refinement Panel’s TaxonomyFilterGenerator Produces Unexpected Results
  1. Chad
    April 23, 2012 at 18:31

    Hi Nick,

    It looks like we’re having the same problem. We’d like to use managed metadata as a “Tag” field for several content types, but have found that as users click the various tags in the refinement panel, instead of refining and narrowing down the results, it generalizes (as more items are clicked, it’s using an OR operator instead of an AND).

    We developed a temporary workaround. We’ve made the managed metadata field a mapped property in search, and then set up a custom refinement category in the Filter Category Definition with each individual term in the term set, and every combination of terms, defined as Custom Filters.

    Have you found a better workaround? Or have you heard anything further from Microsoft? We’re contemplating opening a case ourselves as this more or less renders the reason for us to use Managed Metadata moot.

    Thanks!
    Chad

    • April 23, 2012 at 20:37

      Hi Chad

      That is exactly the problem. Of course even that workaround assumes not too many terms and not expecting users to add any more.

      I raised the problem with their workaround a week ago and still waiting for them to confirm it. Microsoft tried to call me today but I couldn’t take the call as I am currently at the International SharePoint Conference in London. There was no information in their follow up email so I assume there is no progress yet. I will be trying to speak with them as soon as I can and see if we can get some progress and will report back.

      By all means I think it would be worth you raising it with Microsoft too. They are more inclined to work on a problem and resolve it when several people report it. If you want to wait to hear their initial response to me then that will be fine. Please let me know if you pursue this with Microsoft too. I’ll update this when I get further information.

      Thanks

      Nick

      • April 28, 2012 at 09:07

        Hi Chad

        Microsoft have now got back to me and basically don’t want to fix either of these problems and suggested we hire a Microsoft consultant to write a filter generator that works!

        I insisted these are defects and need at least one of them fixed, so now they want a business case written up etc, but is not looking hopeful. The problem for me is that I finish on this project in a week so can only hope for a CU fix to come down the line.

        They did say however that if a few other people report the same problem then they are much more inclined to deal with it. So please go ahead and raise it with Microsoft and give them more reason to work on this.

        Thanks

        Nick

      • Chad
        April 30, 2012 at 16:11

        Hi Nick,

        We’ve opened a case with Microsoft as well. I’ve aimed the technician to your blog so as to show we’re not the only ones with this problem. So far he’s been able to reproduce the problem on his end and is getting additional resources involved. I’m expecting a call either today or tomorrow from him for an update. Hopefully we’ll have better luck, I’ll post back what they find.

        Chad

      • April 30, 2012 at 17:16

        Thanks Chad.

        I have let our Microsoft Engineer know about your case and pointed to the blog too. Hopefully they will link them and give this higher priority.

        Best regards

        Nick

      • Chad
        July 6, 2012 at 19:23

        Hey Nick,

        Microsoft finally got back to us after submitting a request to the product team to have this added as a new feature. It was rejected. We did figure out a (sort of) workaround, where a jquery will hide any other managed metadata refiners once the user selects one managed metadata refiner. It doesn’t completely ruin the point of the feature, but it certainly waters it down.

        Any luck on your end?

        Chad

      • Chad
        July 6, 2012 at 19:29

        Sorry for the multiple replies, but I was just reminded MS revealed to us that the fix would entail a URL change. Check it out…

        http://yoursharepointsite/_layouts/OSSSearchResults.aspx?k=yourquery&cs=This Site&u=http://yoursharepointsite&r=”owstaxIdmms”=#933922bf-9805-4619-bae0-c5411ef0688a:”term1″ “owstaxIdmms”=#5a4745f1-39e2-4413-b715-b3f0236c5752:”term2”

        …is the URL when a managed metadata refiner is clicked. Now, add an “AND”…

        http://yoursharepointsite/_layouts/OSSSearchResults.aspx?k=yourquery&cs=This Site&u=http://yoursharepointsite&r=”owstaxIdmms”=#933922bf-9805-4619-bae0-c5411ef0688a:”term1″ AND “owstaxIdmms”=#5a4745f1-39e2-4413-b715-b3f0236c5752:”term2”

        …and results return as expected: all results returned have both the first and the second refiners clicked on.

        I’m rather astounded that the fix would literally entail adding a checkbox or somethign to the UI so users would be able to select the desired behavior and they aren’t going to do it.

        Chad

      • July 6, 2012 at 19:43

        Hi Chad

        Unfortunately we were unable to get any progress on this. Thanks for the information. So is this change that they are making going to appear in a CU?

        Thanks

        Nick

      • Chad
        July 6, 2012 at 19:46

        Sorry I wasn’t clear – they are not making a change. Yet, the behavior I described with the URLs works right now! That’s why I’m astounded they won’t just follow-through by providing a checkbox or something in the UI so we can choose the AND/OR behavior as desired.

      • July 6, 2012 at 19:56

        I see. It would be good even if they could create a property in the property bag of the search site or the web app or something like that which by default can be off then we can turn on this behaviour if we want it without affecting others or requiring a checkbox or other UI change. That would be the simplest change.

        Thanks for the update.

  2. Aisza Bernadette
    September 11, 2012 at 07:52

    Hi,

    I would like to ask, if it is possible to restructure the UI of the Refinement Panel Web Part to a dropdown? Like in the search results webpart, you can update the xsl.

    thanks.

  3. DanM
    May 24, 2013 at 01:25

    Was there ever any progress on this? We’re facing the same issue here and it’s a bit of a show stopper. Any Javascript gurus who might be able to provide an onclick handler that rewrites the URL as adding the ‘AND’ does work perfectly?

    • May 24, 2013 at 06:16

      Hi Dan
      Unfortunately no progress. The client ended up accepting the issue for now and will raise it again with Microsoft if users start to complain.
      Thanks
      Nick

  4. Eliya Amanoeel
    July 16, 2013 at 08:55

    Hello,

    How can i manage to add icon to each custom filter category? Yes there is a special field for this purpose in Refinement Panel web part settings but i seeking some solution through CSS or XSLT. Any help would be really appriciated.

  5. Cosmin Barbus
    April 4, 2014 at 12:26

    Hi everyone,

    I had a similar issue. In order to solve this problem the following steps were made:
    – custom CoreResultsWebPart
    – override ConfigureDataSourceProperties method
    – get refiners from QueryString and append as a regular query

    public class CustomCoreResultsWebPart : CoreResultsWebPart
    {
    protected override void ConfigureDataSourceProperties()
    {
    var dataSource = this.DataSource as CoreResultsDatasource;
    dataSource.SupplementalQuery += ” \”Article\” \”Policy\””;
    }
    }

  1. May 14, 2012 at 13:41

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

w

Connecting to %s

%d bloggers like this: