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

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

Added Metadata (Taxonomy) to Document Type at Top Level Site Collection; How to break inheritance at

Posted By:      Posted Date: October 19, 2010    Points: 0   Category :SharePoint

We're really loving the ease with which we can add site columns to content types, and have them propagate through all lower-level sites. This is awesome, especially when combined with taxonomy in the term store!

However, our Intranet is to feature a publishing site with subsites to house inter and intra-departmental, private working groups who develop material outside of the public Taxonomy term store and outside of traditional requirements for taxonomy data. This covers a specific area of navigation; the RED HIGHLIGHTED navigation and sub-navigation (not pictured) should all exist without the taxonomy column requirement required of all other sites and subsites.

Example: http://ctnation.citizenschools.net/DotNetNuke/images/WOW_Sample.jpg 

In building the site template for the Workspaces sites, I want to remove all requirements for all content types for the public-site-wide-taxonomy. However, when I edit the content types at the sub-site level, there seems to be no ability to break inheritance from the parent information, and thus, all content types require the taxonomy column (as defined at the root-site level). 

Given the need to remove the site column from all content types, libraries and lists in this Work

View Complete Post

More Related Resource Links

content Type at site collection level using feature.

I m planning to create a feature to install the content type and site colomun at site collection level. Now my doubt is? 1. what will happen when i de activate a feature with documents already there? 2. what will happen when i de activate a feature without documents? What are points i need to take care? 

How to all the Subsites and Site Collections under a top level site collection using client object m

Hello Everyone, I need to know how to get all the subsites and the site collections under a top level site collection using client object model in SilverLight. When I use WebCollection webcoll= ctx.Web.Webs I'm getting the getting subites but i'm not getting the RootWeb and Othe SiteCollections created under the Top Level site collelction.

Restoring from Site Collection Recycle Bin - Item Added

When I restore a list item from the normal recycle bin I can access the item using properties.ListItem. However, when restoring from the Site Collection recycle bin, the listitem is null?! Ok, I thought, the SPItemEventProperties object I have also provides me with WebUrl, ListId and ListItemId so I can spin up a new SPSite with WebUrl, use openweb to get my SPWeb, use ListId to get the correct list and then the ListItemId to get the item. A bit long winded but should get me where I need to be. This would be ok, but at runtime I got an exception list not found. On investigation it seems the WebUrl property is wrong. I've run this on a few different lists/sites and it is consistently wrong! The value I'm seeing is http://[webapp]/sites/[sitecol]/sites/[sitecol]/[web]. Note the repitition of /sites/[sitecol]?! This is really frustrating and very poor. So not only is the ListItem property null(?), but there is no easy way to get the list item manually! Does anyone else see this behaviour? Sharepoint is really testing my sanity this week!    

Users (even site collection administrator) unable to see minor versions in document libraries


I have document libraries with the following settings: major & minor versioning enabled, checkout required & 'only users who can edit items' can see draft (minor) items. The problem is when a user uploads a document (the first document), the library appears empty. However, looking at the summary in 'view all site content' we see that the number of items in the list has incremented by 1. Typically, if the user selects explorer view they can also see the document they just uploaded.

Similar behaviour occurs using the 'New document' option. Before checking in the document for this first time it is visible in the library. If it is checked in as v 0.1 it 'disappears' if it is checked in as v 1.0 it is visible.

I have noticed that if I toggle the Draft Item Security setting by setting it to 'any user who can read items' then set it back immediately to 'only users who can edit items' that the previously hidden items become visible. And any new minor versions created subsequently are also displayed correctly. I can of course do this for existing libraries, but if new libraries are created based on my template this behaviour reoccurs.

Has anyone seen this before?

Restore Site Collection on a Different Farm with Taxonomy Field



I am trying to restore a site collection from my production environment into a staging environment (completely separate farm).  However, my site collection contains a Pages library which has a taxonomy field that points to a Managed Metadata Service term store in the production environment.  When the site collection is restored in the staging environment, the items in the Pages library have invalid content in the taxonomy field.  Ie. The values are there, but when I try and edit an item, the values in the picker are invalid. 

I have imported the same term set in the term store in the staging environment but it still doesn't work.  I am assuming it is because all of the terms have different guids in each environment so the values are not 'synching' up properly... 

Can I restore the Managed Metedata Service application from my production environment into my staging environment?  Or, am I going about this process in the wrong way entirely?

Thank you for any advice.


Activating Publishing Infrastructure at the Site Collection level


My task is to my company's branding solution to two new sites. I can upload the solution but I cannot activate it. I can't activate it because SharePoint Publishing is turned off on the sites. When I attempt to turn on SharePoint Publishing, I get this error:

The feature being activated is a Site scoped feature which has a dependency on a Site Collection scoped feature which has not been activated. Please activate the following feature before trying again: SharePoint Server Publishing Infrastructure f6924d36-2fa8-4f0b-b16d-06b7250180fa
The Site scoped feature being activated has a dependency on hidden Site scoped feature 'FeatureDefinition/22a9ef51-737b-4ff2-9346-694633fe4416' (ID: '22a9ef51-737b-4ff2-9346-694633fe4416'). Hidden features cannot be auto-activated across scopes. There may be one or more visible Site scoped features that auto-activate the dependent hidden feature.

I can't seem to locate the Publishing Infrastructure feature. The Site Collection List provides information about each site collection but no access to their features. How do I turn on Publishing Infrastructure?

URGENT: Document Library Content Type not inheriting some fields from parent Site Content Type


I have a situation that has foxed me!! I have a site level content type that has 8 fields... I use this to create more content types at the site level and use these in multiple Document Libraries (I have 40 doc libs).  This works fine for 38 of the libraries.  But for 2 of them... 2 of the columns are not showing up on the document libraries.  These are user lookups fields.  I am not sure why it's not working in these libraries only!  When I use the same content type in another library... the inheritance does not break for these fields!

Anyone please provide some guidance on this?  I am using WSS 3.0 and SPD to do workflows.

On another note... the content type has a template (in excel) attached to it.  When I create the content manually using the content type from the New menu option, the template is used... however, when I try to add it using an SPD workflow, it creates a blank template... the content type template is not being used.

Please help... I am in a fix and need to release this application today!!!

Maximum number of Document libraries or Lists that can be created in a Site collection of sharepoint


Hello Guys, 

what is the maximum limit for creating document libraries in sharepoint 2010, is there any limit? if so can you give me the number and details where do i find it.

Thanks in advance.

disable top level site collection


I saw some compaies when they created sharepoint web application, they do not create a top level site collection.  thety created site collections under managed path. For example, the sharepoint web app called http://MyCompanyNmae.com. users can not access http://MyCompanyNmae.com directly. Instead they have to access through






Why they disable the top level site collection? for what purpose?


Thanks in advance,  


Remove List Field Type under site collection


Hi All ,

We have a custom field created and added the same under a webapplication , now I would like to remove this field type from a specific site collection , can anybody suggest as how to go about the same .





How do I pre-populate document quick parts based on site metadata?


Anyone have any thoughts on how I would populate data into document quick parts?

The answer seems pretty simple with content types and such, but the complication is that I want to pull in contact information from a list local to the site in which the library resides.  For example:


A project site is created.  The company's contact information is copied down to the site via the site creation process.  A Letter Standard content type is managed throughout the site, and pulls the contact information from the list and populates the appropriate pieces within the document automatically.

Anyone done something similar to this?

permissions at the site collection level


I am the collection administrator of a site collection called "Teams" .  By default, when the collection was created, Teams Owners, Teams Members and Teams Visitors was created.  Do these permissions only apply to the site collection "home" page, or do they apply to any new sites added to the collection (unless inheritance is broken during the creation of those other sites in the collection)?


There are no mistakes; every result tells you something of value about what your are trying to accomplish.

External Data Option Not at Site Collection Level


Hello all,

It appears that I can only create an External Data field at the library level for a content type. Can anyone validate if this is true. Following a good practice of creating all content types and site columns at the Site Collection I used for my Content Type Hub allows me to create content types/columns only once and have them sent across to any libraries they have been added to.

In the current scenario, if I need to use a Content Type with External Data, in lets say, 12 other libraries, I have 12X the work!

Custom Timer Job provisioned at Site Collection level


Is it possible to have a custom timer job provisioned at the site collection level?  In writing my custom spjobdefinition, it looks like you can only create the timer job at the web application level:

    public KBRankingTimerJob(string jobName, SPWebApplication webApplication)
      : base(jobName, webApplication, null, SPJobLockType.ContentDatabase)
      this.Title = jobName;

My feature receiver is defined as a site collection feature, so I can activate it at a site collection level, but my timer job is being provisioned and running once for each content database within the web application (it seems).  I'd like the timer job defined for just one particular site collection (the one the feature receiver is activated at).  Is this possible?  Or am I stuck at the web app level?

If I am stuck at the web app level, how has anyone created a timer job to run against 1 particular list within a site?

New site columns added using xml,not shown in existing site collection


I have added new site columns to the existing content type using xml,deployed to a sharepoint application as a feature using VS2010. Now my problem is the site columns are not updated in existing pages under site coolection,it is showing only the existing site columns and not the new site columns. I then tried adding those site columns to the pages library manually,after that it is displaying those columns in pages and i can enter text in edit mode but whenever i save the page it is rendered with some tags like <span id="msrterangecursor">. It is shown for only new site columns.

Could anyone help with this.

Office Development: Manage Metadata with Document Information Panels


Here the author uses Document Information Panels in the Microsoft 2007 Office system to manipulate metadata from Office docs for better discovery and management.

Ashish Ghoda

MSDN Magazine April 2008

Master Pages: Master Your Site Design with Visual Inheritance and Page Templates


Master pages in ASP.NET 2.0 solve a problem many Web developers have been solving on their own with a variety of techniques for years - providing a single master template for an entire site. This article covers the details of master pages, discussing their usage and implementation and how they are a natural evolution of custom techniques developers are using today.

Fritz Onion

MSDN Magazine June 2004

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