.NET Tutorials, Forums, Interview Questions And Answers
Welcome :Guest
Sign In
Win Surprise Gifts!!!

Top 5 Contributors of the Month
david stephan
Gaurav Pal
Post New Web Links

Content Organizer, Managed Metadata, & Routing to Folders

Posted By:      Posted Date: April 14, 2011    Points: 0   Category :C#

We have the following situation:

When using a Managed Metadata column value to name folders automatically created by the Content Organizer, the Content Organizer creates folders/subfolders for the *entire* term hierarchy from the term to the entry point in the column properties, not just the single value actually entered in the column. Is this expected behavior? If so, it seems quite odd. If not, is there some way to get this to behave the same way it does when using a non-Managed Metadata column?


Documents from a document library are to be routed to a Records Center and placed into a specific folder (Category1, for example). The Content Organizer is configured to evaluate whether a value exists within a Managed Metadata column - if the column is empty the rule does not fire, if the column is populated the rule fires. Assume the Managed Metadata column is called "MMColumn" and points to a branch in our taxonomy named "Terms". The term the user applies to the document is Category1 (chosen from MM) which corresponds to the name of the ultimate destination folder.

Our rule specifies that the document is to be routed to our Records Center. The option to automatically create a folder is enabled with the folder name to be the value from the Managed Metadata column specified above.

Expected behavior is our docume

View Complete Post

More Related Resource Links

Content Query Webpart + Managed Metadata + Public facing site


I have content query webparts to fetch data based on filter on managed metada its work like charm but not working on Public facing site.

i mean on public facing site its not showing data.i check all pages in library are published and also all css and custom .xsl file also published.

please advise me

Thanks Ron

Issue with Content Organizer Routing Behavior


Not so much a question as an open item to Microsoft.

Given a scenario where content is organized into folders within a library and users are given permissions to create items within specific folders, but not the library itself , Content Organizer rules that target these folders will route the document back to the Drop Off Library when evaluated through the OfficialFiles.asmx web service (as Word does).

Manually submitting the file through the SharePoint UI will work fine; the document will be routed to the proper target location.  Any calls to the GetFinalRoutingDestinationFolderUrl method on the web service will route the document to the Drop Off Library if the user does not have Add rights on the target library, even if they have folder level Add rights within the library.


Content organizer rules and calculated metadata in Records Center



I created a Document content-type in which I've added a first "Choice" metadata (column) and a second one which is calculated (Yes/No option) from the first one.
I tested the new content-type in a library and works well.
Actually this content-type was created to use in the Records Center, and more particularly in the creation of new rules to route documents in the Records Center.
Unfortunately, when I want to create a new rule, I can't use the calculated metadata in the "Conditions" section, since it simply doesn't appear in the list of choices from which we can define the rules.

Does someone know why ?
Thanks !

sharepoint search pdf files using metadata and also the content inside pdf

I am a novice to sharepoint search can anyone give some ideas on how to integrate search at a subsite level (only to that subsite) which has pdf documents with metadata associated with it the search should also search the content within the pdf and libraries and list metatdata in Moss 2007

How to maximize use of managed metadata in the document library?

We are creating new Intranet portal based on SharePont 2010 and we have document library with 100-200 documents. Old Intranet is based on previous version of SharePoint. End-users did not like the usability of the document library as it was hierarchical. Users needed to know, which was the folders and its subfolder to find out where is the document. We are currently investigating if we can solve this problem by using managed metadata. We know how to define term set and how to give metadata to the document, but we don't know what is the most usable way to utilizem them in the document library. Let say that end-user would like to see all documents that has managed metadata "User Guide". How to configure document library so that users see only those documents. Not all our users are skilled and we have to provide very intuitive way to search relavant documents to them. Some predefined metadata dropdown would be great.Kenny_I

Setting Managed MetaData default values on site creation

I am working on a project where the requirement is to have specific document content types.  I have therefore create a site columns feature which creates all my columns, I have a Site Contentypes feature which creates all my content type and I have list templates based on my content types.  I also have created a couple of Site definition features which create specific list instance based on my list template As part of my content types I have created a few Managed Metadata fields which I wanted to set defaults for on the creation of my sites.  I have therefore created a feature which is right at the end of the WebFeatures section in my ONET.xml.  This features enumerates through all lists, looking for specific column names(managed metadata columns) and looks to set these to specific values.  The code to set the default value on the field is: TaxonomyField documentCategoryField = (TaxonomyField)library.Fields["Document Category"]; if (documentCategoryTerm != null) { documentCategoryField.DefaultValue = documentLibraryDefault.ToString(); documentCategoryField.Update();                                                     }                         &n

Provision DocumentLibrary with Managed Metadata column

Via the SharePoint 2010 UI I've created a DocumentLibrary and added a new column of type Managed Metadata. I've associated a TermSet with this column and all works fine. Now I need to create a deployment package in Visual Studio 2010. It is easy enough to create the Document Library. I've followed the below steps 1. Create empty SharePoint 2010 project 2. Added new Empty Element to the project. In the Elements.xml I have <Field ID="{15712E76-A603-43AB-885E-CE48BD216381}" Type="TaxonomyFieldTypeMulti" Name="DocTags" DisplayName="DocTags" ShowInDisplayForm="TRUE" ShowInEditForm="TRUE" ShowField="Term1033" Required="FALSE" StaticName="DocTagsInternal" Group="NotSure"/> 3. Added ContentType to the project. Added FieldRef elements to the Element.xml 4. Added List Definition From Content Type and associated it with the above Content Type. 5. Created a List Instance of the above List Definition. 6. Build and Deploy. 7. Associate the column with a Term Set. 8. Add Document to the Document Library. I can select a Term from the applicable TermSet, but when I save the document I get: Failed to get value of the "DocTags" column from the "Managed Metadata" field type control.  See details in log. Exception message: Invalid field name. {00000000-0000-0000-000

Can Managed Metadata columns be edited in the DataSheet View of a Library or List?

Hi, I like to mass set document properties in a library using DataSheet View, the properties are columns based on Managed MetaData values. When I open the doc library in Datasheet view, those columns become read-only. I made sure the library does not require 'Check Out' and also tested it in other views then the AllItems view. Can someone confirm what is the expected functionality and or if there is a bug?

Need to link multiple External Content List items to a single document metadata column

I have an external content list - for my purposes, the data isn't any fancier than a list of terms provided by a web service (read only - I don't need update/delete functionality). I want to be able to link any subset of those terms to a single document metadata column (in other words, I need it to work like a normal content list that is defined to allow multiple values in a column) but SharePoint doesn't let me do that on an ECL. I need the content list to be externally driven since more values are going to be added to an outside system over time, but I think it's possible that I may not need a full-fledged ECL list to make this work this way in SharePoint. Just to clarify: I don't need the metadata values in my documents to maintain a PERSISTENT link to the web service (if someone changes an underlying value in the web service DB, it doesn't need to be updated in the document table too). I just want SharePoint to offer up an updated set of source values from the web service if somebody goes in and edits the document metadata. Any ideas for how I can make this work?

search on managed metadata column values

I am trying to search on a managed metadata column in a list.  I have the managed metadata as a mapped property (these are automatically set up actually). I have a column frequency (daily, weekly, monthly, yearly) I can enter a search box owstaxIdFrequency=#a132a333-39f1-4737-9ad4-a932482e025f   //this is the taxonomy guid for Daily.  This shows results. How do I search on the word "Daily" in the frequency column?  (I just want to figure it out on a simple search first meaning just using one search box)   I noticed that there are extra maped columns for managed metadata columns (owstaxIdFrequency also has owstaxIdFrequencyx0020Tag, I tried owstaxIdFrequencyx0020Tag="Daily", but it didn't work)

Moving Managed metadata

If i create a managed metadata taxonomy structure in my test environment how can i get this copied into my production system? TIA DeanDean MCTS-SQL 2005 Business Intelligence

Managed Metadata columns in Sharepoint Workspaces

Hello,   all our document lists use Managed Metadata columns. They are required also.    Sharepoint Workspaces list current values for these columns, but do not allow changing them. Thus effectively making Sharepoint Workspace unusuable, because we can't check-in new documents.   Am I missing something?

Update Managed Metadata Field with using Lists.asmx service

Hello! I am trying to update Managed Metadata Field with using Lists.asmx. I know that I must use this format WSSID;#VALUE|GUID. But I don't Know how I can get WSSID and VALUE Guid! Can I get them with using lists.asmx! Thanks!!

Can Managed Metadata columns be edited in the DataSheet View of a Library or List?

Hi, I like to mass set document properties in a library using DataSheet View, the properties are columns based on Managed MetaData values. When I open the doc library in Datasheet view, those columns are read-only. I made sure the library does not require 'Check Out' and also tested it in other views then the AllItems view. Can someone confirm what is the expected functionality and or if there is a bug? Should I be able to edit them in 2010 and were they editable in 2007 version. Please help. thanks. I came across this other post which suggests that functionality is not available ? pls someone confirm. Mass-editing metadata when documents are uploaded (individually or in bulk) to MOSS 2010  

Is it possible to implement your own version of the Managed Metadata Service?

Hi, It would be nice to provision a new instance of the Managed Metadata Service where the service is not implemented by Microsoft.SharePoint.Taxonomy.MetadataWebServiceApplication, but a custom provider. Is it possible to expose your own service as a Managed Metadata Service?

Multilanguage managed metadata filter

Hi, I wonder, how to create filter for view, using managed metadata in multiple languages. For example I have list with managed metadata column "color" with content "red", "yellow"... When I switch the language to german, it changes to "rot", "gelb" and so on for all other languages. Now I want to filter all list items with red color. But it doesn't work in other languages. So question is, how to set value of the managed metadata column? If it is "red", I switch to german language and it doesn't work. When I set "red" or "rot" it works, but it is nonsense set all filters for all languages and change it every time you add new language pack (we need 15 languages). Is there any possibility to filter items by key and not actuall value in actuall language? Thanks.  

Sharepoint Managed Metadata Services and Office 2007

Is there a patch or a workaround which would allow you to fill in metadata information pertaining to a column(which is a managed metadata type) from office 2007 client application. Currently it is greyed out and says Edit in server. Thanks KI am what i am
ASP.NetWindows Application  .NET Framework  C#  VB.Net  ADO.Net  
Sql Server  SharePoint  Silverlight  Others  All   

Hall of Fame    Twitter   Terms of Service    Privacy Policy    Contact Us    Archives   Tell A Friend