Tell me more ×
SharePoint Stack Exchange is a question and answer site for SharePoint enthusiasts. It's 100% free, no registration required.
up vote 1 down vote favorite

In SharePoint 2010, I have a standard Announcements list on which I have enabled Audience Targeting. When a list view is setup to display the Target Audience, it renders as a GUID, not as the display name of the Audience. Has anyone been able to fix this?

share|improve this question
Update: I've just found that some list items do display the display name of the audience. In fact, I have an example with a list containing 5 list items. If I set the audience for 4 of these to the same value, they all display the audience name fine. However, when I set the last list item to the same audience, they all display GUIDs. Really weird. – Biilmann May 25 '11 at 13:29
Update: It seems that setting the audience for the most recent list items causes this behaviour. I can successfully set the target audience for older items (>2 days old). But I if try to set target audience for the more recent items, all list items' audience column display as GUIDs. – Biilmann May 25 '11 at 13:36
did you ever get a definite solution to this problem? I now have the same issue in a SP2010 environment (no update from SP2007). We are already on SP1 + CUdec2011 Would love to get an answer. – user7161 Feb 29 '12 at 16:18
No, my status is the same. As Lisa points out below, the workaround is to avoid targeting the first item in the view. We are on SP1 now, but I have not had the chance to test this again. Sounds like you did, with no luck, though. – Biilmann Mar 6 '12 at 20:49

3 Answers

up vote 0 down vote accepted

I've experienced the same thing... I've noticed that it only happens when the first item on the list or library is targeted.

I had a list where item # 1 had no targeting and a few others did. It all looked fine until I targeted the first item and then all the items got messed up. I removed the targeting on the first item and all went back to normal.

I then experimented some more: I targeted an item further down the list, leaving the first one untargeted and everything was ok, but then I sorted the list by modified (instead of name) and hey presto... GUIDs again!!

So basically, targeting the first item on the list is what messes things up!

share|improve this answer
Thanks, Lisa. You're absolutely right. In my setup, targeting the first list item also messes up the display. We're not on SP1 yet. Don't know whether this is something that SP1 fixes. (marked as answer, since this is as close as we can get, IMO). – Biilmann Aug 9 '11 at 8:48
up vote 1 down vote

I have seen this when audience rules were based on distribution lists rather than "real" compiled audience rules

share|improve this answer
Ok, thanks, but it is a compiled audience. It's a single audience that includes all users from our AD. I think I'll try to add another audience, based on a specific AD property, assign this for some list items, and see if that changes anything. – Biilmann May 5 '11 at 19:26
up vote 0 down vote

Is the database from 2007 that was upgraded using the db attach method? If so you need to update the SSP database when creating the User Profile service to import the Audience from 2007. More info here.

share|improve this answer
No, we have not upgraded from 2007. The audience I'm using here was setup from scratch and compiled succesfully with 298 members currently. – Biilmann May 5 '11 at 19:28

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.