2

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

  1. Rename our custom field? or
  2. 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 8:27
  • @Aanchal That's true – Benny Skogberg Sep 22 '14 at 9: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.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

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