Take the 2-minute tour ×
SharePoint Stack Exchange is a question and answer site for SharePoint enthusiasts. It's 100% free, no registration required.

My issue is that I have two lists that I would like to move with their data. While I am able to save both as templates and then upload to the new site, none of the lookup columns in my parent table are populated with data now. Can this be done?

share|improve this question
add comment

4 Answers 4

up vote 3 down vote accepted

Not to my knowledge. I've always chalked this up to that when the lists are saved, the look-ups are dropped because there is no guarantee that when the lists are provisioned, that the other dependent list will exist, so it can't save the data.

Something I've been meaning to try is to provision the lookup list first then provision the main list and see if the data will still exist. My inclination is that it won't. However, if you export the main list to Excel, provision the list from the template, then go into datasheet mode, you should be able to paste the data from Excel into the list and be back up and running.

share|improve this answer
    
yup, this seems like the only way... very pitty tho, especially if you have large amounts of lists/data –  int32 Aug 17 '11 at 7:59
add comment

please look at the link below

http://techolyvia.wordpress.com/2010/07/29/export-list-template-not-retaining-look-up-column-values/#comment-179

share|improve this answer
    
While this may theoretically answer the question, we prefer inclusion of the essential parts of the answer here, and to provide the link for reference. See answer for general guidelines. –  SPDoctor Jun 3 '13 at 8:17
add comment

I have the same need. I've come across this solution: https://danielthenerd.wordpress.com/2012/06/14/list-template-lookup-by-list-name-not-guid/

Basically, taking the STP, converting it to a CAB, extracting the Manifest.xml, editing it so that the GUID reference is replaced by a name, since the GUID is auto-generated at "run-time".

<Field Type="Lookup" List="Lists/NameOfListToLookup"/>

This works, when creating lists manually (via the UI) - the lookup is preserved.

In our case, I'm trying to create lists via a Visual Studio-generated WSP (feature which dumps the STPs, instantiates lists), with an event receiver to create the lists (List being looked up and another list referring to the first). We were also able to create the lists with the WSP "method".

share|improve this answer
add comment

Gary LaPointe has written some particularly ace extensions to stsadm that allow you to import, export, and copy lists (among many other things).

The documentation for these commands can be found here: Import/Export/Copy Lists

I've used these in the past to move lists containing lookups around successfully; I'm pretty sure the lookup values and IDs had an option to be preserved.

share|improve this answer
add comment

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

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