Thanx to Bill Seagle, CMS Illinois
In the grand scheme of things, the audience has always been a welcomed feature. The fact that audiences are used throughout the MOSS 2007 solutions has been very attractive.
Equally important, providing our customers/users with the option to leverage the audiences has brought tears to my eyes. In simpler terms, I must admit that I have been pushed into a reality to accept the fact, that all is not perfect.
Indeed enabling audiences on a library allows the user to target content to a specific group of people, on the other hand, we have found is that when configuring audiences on a document library with multiple content types, it only activates audiences for the first content type in the list.
In order to duplicate this, perceived, challenge. You must configure a document library with; at least, two content types (see Content Types 1)
In addition, you would need to have two items in your library. The next step is to configure each item with a separate content type (see Content Types 2 and Content Types 3).
Next, you would navigate to the document library’s Audience settings. Select the “Enable Audience Targeting” (see Content Types 4) option and click on the OK button.
To verify the activation of “Audience Targeting”, you would need to ensure that you have navigated to the “Document Library Settings”, “Columns” section. Verify that the “Target Audiences” column is added. Also, note that the column only applies to the first content type added to the library (see Content Types 5).
Note: The Document content type is added to the document library during the time of creation.
At the same time, you can verify the configuration of the audiences by viewing the properties of the two items in the document library (see Content Types 6 and Content Types 7).
Note: The two items must be associated with one of the content types associated with the document library.
The fix:
In order to bandage this problem is to navigate to the “Site Content Gallery“. You would have to add the Target Audience column to the content type missing the much needed column (see ContentType 8).
Note: Don't forget to force the modification down to every instance of the content type.
