我们的客户要求我们更改列表视图过滤,以显示托管元数据中的分类系统中的所有术语,而且只显示库中的文档。

目前我们有两列:

我们有一个由术语分类填充的托管元数据列。在列上使用过滤器时,来自分类学的所有值都是可见的。

我们还有一个自定义字段定义列,它从CaRouonyfield继承,在筛选视图中,只显示库中存在的文档的值。

我试图找到提供此过滤的方法。搜索后,看起来没有简单的方法来为托管元数据列执行此操作。看着网也没有给出任何完全答案。我只发现了一个人问同样问题的地方,但答案对我的案件并不令人满意。

列表视图过滤在Manged Metadata字段中

有帮助吗?

解决方案

We were finally able to resolve the issue. In short - to work you need to change the way how OOTB Filter code works to way that it thinks that it is operating with SPFieldLookup.

To achieve this you need 3 steps.

1.Create copy of Filter.aspx file located from Sharepoint Root Directory. This aspx is responsible for rendering items in filter view. 2. Create HttpModule to redirect requests to the customFilter. 3. Register created HttpModule in webconfig.

  1. Replace FilterAspxPage class (the code is in Microsoft.Sharepoint.ApplicationPages.dll) used in this aspx file with custom implementation, which should look like this:

    public partial class CustomFilter : Microsoft.SharePoint.ApplicationPages.FilterAspxPage
    {   
        protected new void GetDistinctValues()
        {
        // exact copy of the method GetDistinctValues from Microsoft.Sharepoint.ApplicationPages.dll with code taken from OnInit method
        // to properly initialize objects used in this method
        // Also one use of reflection was needed, because renderAsHtml is protected
    
        // after assignment to text4 string we've added this condition:
    
        if (text4.Equals("Microsoft.SharePoint.Taxonomy.TaxonomyField", StringComparison.InvariantCultureIgnoreCase) == true)
        {
            text4 = "Microsoft.SharePoint.SPFieldLookup";
        }
      }
    }
    
  2. Here is an example of how to create custom HttpModule:

    public class ListFilterRedirectModule : IHttpModule
    {
    
    #region IHttpModule Members
    
        public void Dispose()
        {
        }
    
        public void Init(HttpApplication context)
        {
            context.BeginRequest += new EventHandler(context_BeginRequest);
        }
    #endregion
    
    
        private void context_BeginRequest(object sender, EventArgs e)
        {
            HttpApplication application = (HttpApplication)sender;
            HttpContext context = application.Context;
    
            if (context.Request.RawUrl.IndexOf("/_layouts/filter.aspx", StringComparison.InvariantCultureIgnoreCase) >= 0)
            {
                string newUrl = context.Request.Url.Scheme+"://"+context.Request.Url.Host + context.Request.RawUrl.Replace("/_layouts/filter.aspx", "/_layouts/CustomFilter.aspx");
                context.Response.Redirect(newUrl);
            }
        }
    
    }
    
  3. You will need to configure this module in the web.config file of your web and register it with IIS before being able to use it. For more information of the whole process see the following link: http://go.microsoft.com/?linkid=8101007. Below are sample lines that you can add to the web.config file:

    <system.webServer>
        <modules runAllManagedModulesForAllRequests="true">
            <add name="ListFilterRedirectModule" type="ListFilterRedirectModule, ... , Version=1.0.0.0, Culture=neutral, PublicKeyToken=..." />
        </modules>
    </system.webServer>
    

其他提示

You may use this solution from CodePlex: http://metadatapagefilter.codeplex.com/ It has quite some limitations (column must exist as root site, limited to term sets with one level ...) but maybe it can help you.

Read the discussions if you are using IE8 or 9 as it indicates how to work around a infinite loading situation.

许可以下: CC-BY-SA归因
scroll top