3 Comments

  1. So good I stumbled up on this description Stefan, great description.
    We happen to have a similar issue with metadata navigation and key filters, in 2010 except ours is inherent to a Custom List.

    3 managed metadata columns of (single value,multiple value,multiple value)type, the item count vs. returned items are messed up as soon as a combination of metadata navigation and filtering is applied and paging is gone as well in most cases.

    When the view definitions themselves contain a filter, then a metadata filter applied on top of the view as well invokes the same issue.

    I have not been able to work out how the calculation goes wrong as nicely as you did, but I hope the root cause may be similar and we may be able to have it fixed based on your trail.

    Reply

    • Glad that i could help actually there are also some other small problems with manage meta data. With more an more filter applied to the view, the url gets longer and longer. If it gets to long then the view is broken too. I think could check this too. You will find some good information about that in the technet.
      The best way to filter would be if SharePoint sends a post request but currently its the GET Methode.

      Reply

  2. Thanks, the technet article is useful too. Fortunately the length restriction does not apply to the parameters, and they are URL encoded as well.

    The views do handle 10+ values in combined metadata filters, at least they render, but the displayed result is incorrect regardless of the complexity of the filter parameters.

    I really hope that this CU has not yet been applied to our environment, because then it may be fixed quickly by deploying it or, by our SP patch arriving still in April. Fingers crossed.

    Reply

Leave a Reply

Required fields are marked *.


This site uses Akismet to reduce spam. Learn how your comment data is processed.