Skip to main content
SharePoint

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

4
  • The Field office choices should only be relevant to the region. Each site maintains their own list of field offices. I'm not sure this would work. Commented Mar 21, 2011 at 19:49
  • Ah right, Field Office is a lookup, gotcha. The only option I think is to have separately named columns - or you could separate each region off into their own Site collections, but this might have issues when you want to roll up across regions. Commented Mar 21, 2011 at 20:04
  • The site collection suffers from wild wild west syndrome. The option to re-architect isn't an option here. You know how that goes. Really is quite frustration that you can not have duplicate site column names in separate groups. Commented Mar 21, 2011 at 20:13
  • Absolutely - I have had this problem before but in the heat of the moment (lol), I just thought "f*** it, I'll use another name...". It is quite daft though how that even thought column has a GUID and an InternalName, both unique, the Display Name still needs to be unique. Commented Mar 21, 2011 at 20:21