Ask a questionAsk a question
 

AnswerLookup Fields problem. Can't save as a template.

  • Tuesday, November 11, 2008 8:28 AMpavlenych Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Hi guys. Since i found out this site it became my favorite one.

    Today i have a little problem with lookup fields. I created a list with, lets say 20 items within. Additionally i created lookup field. When i create a template of the list my lookup field losts the relationship.
    I can fix it by removing the lookup field and creation the new one, but there is some one else who must to administrate the site and he stiil hasn't appropriative skills to do it.
    How can i save this list without loosing lookup field relationship?
    Thanks.

Answers

  • Tuesday, November 11, 2008 4:19 PMSS AMVPUsers MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     Answer

    The real problem occurs when you are in production environment. The lookup field has to be recreated. The solution is to create a WSP package and deploy the list through this WSP. Of course, if you are in dev or test environment, recreating the lookup column is an easy solution but for deployment in production, you must create a WSP.


    SSA - http://sharepointblogs.com/ssa

All Replies

  • Tuesday, November 11, 2008 3:21 PMJennifer Mason Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    I tried to recreate your error, however I didn't have any issues.  Can you tell me more about your situation?  What are the properties of the lookup list, are you using the template in the same site or site collection?
    ~Jennifer Mason My Blog
  • Tuesday, November 11, 2008 4:19 PMSS AMVPUsers MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     Answer

    The real problem occurs when you are in production environment. The lookup field has to be recreated. The solution is to create a WSP package and deploy the list through this WSP. Of course, if you are in dev or test environment, recreating the lookup column is an easy solution but for deployment in production, you must create a WSP.


    SSA - http://sharepointblogs.com/ssa
  • Friday, September 25, 2009 7:09 AMVuthy Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
  • Friday, November 06, 2009 10:47 PMEric Sammann Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    I have been having this same problem.  I have several lists that lookup to other lists in a site that I am trying to make a .wsp template from.  I have not been able to get it to work.  I was trying on the developed site for quite a while before I had the thought of trying it on a real basic site.  The developed site has 15 lists (about half use lookups), two doc libraries, a survey, and 11 SPD workflows.  Every time I would try the deploy would work fine, but site creation would fail.  The resulting site would have all list and libraries, and web parts would be relinked, but lookups would not even show up in the list.  Finally I tried a basic team site with two custom lists, and sure enough the lookups would not copy there either.

    The weird thing is that a template created in SharePoint (.stp) will keep lookups, but break SPD workflows and data views.  An application template (.wsp) will fix dataviews, but breaks lookups and therefore breaks workflows too.

    So same question as pavlenych, which has not been answered in my opinion (on this thread anyway).  How do we save a site that includes lists that have lookups, withouth loosing the lookup relationship?