Skip to main content

Error: A duplicate field name "xxxx" was found

Soon I have some experience with migrating solution from SharePoint 2010 to SharePoint 2013.

The migration was on 3 steps. First one was just to copy the custom fields, content types and list definitions from the old VS 2010 project into a new VS 2012 project for SharePoint 2013. Looks like pretty simple task but …..

The problem:  Error “A duplicate field name "xxxx" was found” when the feature for provisioning the fields and content types is activated.

The solution: Review the field definitions and make sure no field has Name property equal to some of the ‘reserved’ values.

Explanations:
In SharePoint 2010 there was no problem to have these fields as a definition of custom fields:
<Field    Type="Note"
    ID="{893FB9BC-2DA4-4451-A1D1-88010CDC6A08}"
    Name="Description"
    StaticName="Description"
    DisplayName="Description 1"
    Required="FALSE"
    MaxLength="1024"
    Group="Group 1" />
  <Field    Type="Note"
    ID="{854FBE55-1282-43A6-9D98-3EE5EB21597D}"
    Name="Description"
    StaticName="Description"
    DisplayName="Description 2"
    Required="FALSE"
    MaxLength="1024"
    Group="Group 2" />
Here, the Name and Static Name are equal while the ID property is different.

If you move this in the SharePoint 2013 solution the error “A duplicate field name "Description" was found.” will appear on feature activation.
Even if you remove the second field and deploy only the first one - the error will appear !
The interesting part here is that we still can have fields with one and the same Name property but they should not be from the ‘reserved’ once. I have determinate three of these ‘reserved’ fields while migrate - Description, StartDate, EndDate. 
If we change the above definition to the following one, the deployment will succeed:
<Field    Type="Note"
    ID="{893FB9BC-2DA4-4451-A1D1-88010CDC6A08}"
    Name="MyDescription"
    StaticName="Description"
    DisplayName="Description 1"
    Required="FALSE"
    MaxLength="1024"
    Group="Group 1" />
  <Field    Type="Note"
    ID="{854FBE55-1282-43A6-9D98-3EE5EB21597D}"
    Name="MyDescription"
    StaticName="Description"
    DisplayName="Description 2"
    Required="FALSE"
    MaxLength="1024"
    Group="Group 2" />
Even if this will succeed I will suggest you two things:
     first – keep Name and Static name equals
     second – don’t use fields with equal Name property. We can move ahead with only one field. Also using the web interface for editing them we will experience the following behavior: editing the second column listed in the Site Columns page will edit the firs column. What I mean?

If we deploy our fields we will see the following:


If we click on the field “Description 2” we will see this:



The reason is that the page for editing field’s setting use the Name value as a query parameter so the first column that match the Name will be loaded.

Comments

Post a Comment

Popular posts from this blog

ClientPeoplePicker in SharePoint 2013

Start using SharePoint 2013 I noticed that the way for selecting people or groups is changed.
The new way is simple – just ‘Enter name or email address’ without any icons for ‘Check Names’ or ‘Browse’. I guess that the PeoplePicker is changed but NO. PeoplePicker sitll has the same functionality as before.
There is a new control called ClientPeoplePicker.

How to use it:
1.Add this references

<%@RegisterTagPrefix="wssawc"Namespace="Microsoft.SharePoint.WebControls"Assembly="Microsoft.SharePoint, Version=15.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c"%>
2.Add the following control declaration


      <wssawc:ClientPeoplePicker Required="true" ValidationEnabled="true" ID="peoplePicker" runat="server" InitialHelpText="<%$Resources:wss,aclinv_PickerIntialHelperText%>" VisibleSuggestions="3" Rows="1" AllowMultipleEntities="false" CssClass

The column name that you entered is already in use or reserved. Choose another name.

The problem: 
You want to create column with a specific name in SharePoint but SharePoint gives you the message "The column name that you entered is already in use or reserved. Choose another name."



Why this is a problem?
Because you need to create custom columns and content types using the default SharePoint interface.
And the business users have to see properly named columns - for example "Description", not "My Description".

Solution:
It is important to know something technical about SharePoint (versions Office 365, 2013, 2010):
 - it supports columns with same Display Names.
 - you can’t have columns with same Internal names

Let’s implement the following common scenario:
You are creating a SharePoint customization and you need the following column:
   Type: Multiple lines of text
   Internal Name: MyProjectDescription
   Display Name: Description

 Here is the correct way to achieve it:
1. Create the column MyProjectDescription.
This will create column with I…

Office 365 Migration API: how to migrate the taxonomy metadata

If you wander whether the Office 365 Migration API supports migration of taxonomy metadata, the answer is YES. The API supports it but there isn't good documentation about how to modify your xml files after the command ConvertTo-SPOMigrationTargetedPackage.

In this post, I'm going to show you the approach. I assume that you have base knowledge of how to use the Migration API.

The scenario I'm going to use is simple - migrate single Document library with single document.
The document has one taxonomy column (MyTaxonomy) and three versions:

Here are the steps:

Step 1: Export the document library

Export-SPWeb "https://portal.cosingens.com/" ` -ItemUrl "/Shared Documents" ` -Path "\\cos-dev-03\export1\Export" ` -NoFileCompr -IncludeVersions 4
This command will export the document library and will create the initial package.
The command is not part of the Migration API. It is well know since SharePoint 2010 and is part of the server side obje…