Metadata Navigation and column filtering

%3CLINGO-SUB%20id%3D%22lingo-sub-1118069%22%20slang%3D%22en-US%22%3EMetadata%20Navigation%20and%20column%20filtering%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1118069%22%20slang%3D%22en-US%22%3E%3CP%3EWe%20have%20a%20document%20library%20with%20metadata%20navigation%20enabled.%20Some%20columns%20in%20the%20library%20are%20eligible%20column%20types%20for%20metadata%20navigation%20and%20others%20aren't.%20The%20column%20filtering%20via%20the%20column%20header%20drop%20down%20does%20not%20seem%20to%20work%20when%20metadata%20navigation%20filtering%20is%20also%20applied.%20Has%20anyone%20else%20experienced%20this%3F%20Any%20viable%20solutions%3F%3C%2FP%3E%3CP%3ETO%20reiterate%2C%20metadata%20navigation%20works%20on%20the%20columns%20for%20which%20it%20is%20enabled%20but%20we%20are%20unable%20to%20subsequently%20use%20the%20column%20header%20drop%20down%20for%20column%20types%20which%20are%20not%20eligible%20for%20metadata%20navigation%20filtering.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1118069%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3ESharePoint%20Server%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Highlighted
Occasional Visitor

We have a document library with metadata navigation enabled. Some columns in the library are eligible column types for metadata navigation and others aren't. The column filtering via the column header drop down does not seem to work when metadata navigation filtering is also applied. Has anyone else experienced this? Any viable solutions?

TO reiterate, metadata navigation works on the columns for which it is enabled but we are unable to subsequently use the column header drop down for column types which are not eligible for metadata navigation filtering.

0 Replies