I’m working on a List Conversion. I adding a number of historical records to some active records. To prevent the Person Fields and DropDowns from causing errors, we’ve set up text fields in another
I am adding a number of historical records to a list with active records. The lists contains over 60 fields apiece. To prevent the Person Fields and DropDowns from causing errors, we’ve set up text fields in another
To prevent the Person Fields and DropDowns from causing errors, we’ve set up text fields in another Content Type so they won’t be deemed in error. In the Active List, we’ve defined two content types. The first content type is the normal one based off “item”. The second content type, DRRecHist, was defined at the list-level–also derived from item with no other site columns.
The content type was populated with members within the list settings. (First the list was set under “Advanced Settings”) to allow for the management of content types.
Next DRRecHist was added and the desired columns were added to the content type on the List Level. Instead of the Person Fields and the Dropdowns, we added similarly named text fields.
(The people may no longer be in AD and Dropdowns have been changed, so we wanted to prevent errors in porting.)
All this works as expected, I’ve been able to copy the list items from the historical into the live file. I’ve also had to write a small Nintex Workflow to change the content type of the record after I’ve inserted them. Still no problem.
I would like a simple way to prevent the items of Historical Content Type, called DRRecHist, from being modified.
I’m not worried about modifications to the actual Content Type–that is under control. I don’t want historical data changed.
This project has been an eye-opener on content types. I originally thought of Content Types as just consisting of site columns. After a Content Type is initially defined as a site Content Type–List Columns can be added to it within a given List in List Settings.
