A A A Font Size

Pearls of MOSSy Wisdom

Warning: Bad Things Can Happen When You Try To Copy List Items Between Lists

Came across this little gem of a "feature" in MOSS today. 

One of my users wanted some information in one list to appear in another list.  Fine.  But these two lists were not even close to identical.  Now, one would think that if someone tried to copy a listitem from one list to another list and the columns didn't match then an error would occur.  One would think.  But here's what really happens: the columns in the source list that are not in the destination list are ADDED TO THE DESTINATION LIST!  What's worse is that the NewItem.aspx and EditItem.aspx pages are corrupted and only show the newly added columnns to use/edit.  And what is worse is that this copy/paste operation was done via Manage Content and Structure.  So it's very, very easy for a user to mistakenly do.  Here are the pics to show what happened.

First, I created two lists: SourceTest and DestinationTest.  In these lists I created three columns (Column1, Column2, and Column3 in SourceList and ColumnA, ColumnB, and ColumnC in DestinationList).  I then created an item in each list.

 

 

Using Manage Content & Structure, I copied the list item from SourceList to DestinationList.

 

 

The result shown shows the item is "copied" but the data is missing.  Why?

Because the AllItems view only shows the original columns.  But looking at the DestinationList after the copy shows that the mismatched columns were created in the DestinationList.

It gets worse.  Try to Create a New Item in DestinationList and all you get to add are the "New" columns from SourceList.

And apparently I'm not the only person to have found this.
 
Just wanted to warn you in case you haven't seen this before.
 
And for what it's worth, this beavior has been re-created on both SP1 and non-SP1 MOSS Farms.
You must sign in to rate content.
(Unrated)

Comments

This happens with document libraries as well

The really annoying things is that if you have a document library and are trying to use content types to manage the metadata and you send this to a different document library with a different cotent type, it will add the columns to the destination library as well.
Eric Murriguez at 3/6/2009 2:51 PM
You must sign in to rate content.
(Unrated)

This happens with document libraries as well

The really annoying things is that if you have a document library and are trying to use content types to manage the metadata and you send this to a different document library with a different cotent type, it will add the columns to the destination library as well.
Eric Murriguez at 3/6/2009 2:51 PM
You must sign in to rate content.
(Unrated)

This happens with document libraries as well

The really annoying things is that if you have a document library and are trying to use content types to manage the metadata and you send this to a different document library with a different cotent type, it will add the columns to the destination library as well.
Eric Murriguez at 3/6/2009 2:51 PM
You must sign in to rate content.
(Unrated)

Leave a Comment

You must be logged in to post a comment.
Superstar
Tim Dobrinski
Systems Analyst II
Birmingham, AL
Tim is currently not Twittering about updating his LinkedIn profile concerning FaceBooking his MySpace Page's Status.

Search This Blog

 

© 2012 SusQtech. All rights reserved.
Powered by SharePoint Server 2007 and using the MemberToMember SharePoint Add-On for social media capabilities.