SPBuiltInFieldId Conflict migrating to SharePoint 2013

Question

Our customer has a custom Content Type with the custom field Confidential in the SharePoint 2010 environment. Upon migration to SharePoint 2013, we discovered that Sharepoint 2013 already had that SPBuiltInFieldId.Confidential field.

Should we

Rename our custom field? or
Update our custom Content type to use the BuiltIn field Confidential?

So your static name and internal name both are same? – Aanchal Sep 22 '14 at 08:27 — Aanchal, Sep 22 '14 at 08:27

score 3 · Accepted Answer · edited Sep 22 '14 at 09:20

3

You should rename your custom field in your environment, if that can be done without any conflict or error. There might be some issue while updating a custom field name.

Updating your content type with BuiltIn field Confidential , you will lose your data that is stored in previous fields. So you might need to copy your data from old field to new field.

edited Sep 22 '14 at 09:20

Benny Skogberg

25,542
12
68
163

answered Sep 22 '14 at 08:31

Aanchal

7,885
1
15
20

SPBuiltInFieldId Conflict migrating to SharePoint 2013

1 Answers1