I am trying to migrate a SharePoint list from my source, and pasting it as a folder within an existing list on my target. The list is a "Custom List" template, and I am preserving item IDs. I am not seeing the results I was expecting, and it looks like content may have been overwritten or deleted. What could cause this issue?
If migrating a custom list as a folder, or migrating folders within a custom list, while using the Overwrite and Preserve IDs on items/folders in Lists options, any existing folders or items on the target that have the same ID as the folders/items migrating from the source will be deleted in order to preserve the IDs for this migrating content. This is expected behaviour.
For example, if you are more concerned with maintaining the items and folder structure, you can turn off the Preserve IDs on items/folders in Lists option, which will allow the folders and items to be properly added to the list, without overwriting any content.
Before I can install the Metalogix SharePoint Extensions Web Service I need to know specifically what files are installed, and where. Can this information be provided?
Yes, we can provide some information on what files are installed.
The Metalogix Extensions Web Service installs as a SharePoint solution (.WSP file) that is automatically deployed by the Web Service installer, and pushed out to all Web Front Ends (WFE's) in the farm. Inside the solution file are the necessary files for the Web Service. These files are:
·An ASMX file and two ASPX files, which are put in the SharePoint hive. These three files will be listed under a folder that is added for that specific version of the Web Service. For example, three files will be listed under: C:\Program Files\Common Files\Microsoft shared\Web Server Extensions\[hive_number]\ISAPI\ML\188.8.131.52.
·A DLL file, which gets deployed to the Global Assembly Cache (GAC).
After installation the Metalogix Extensions Web Service sits idle on the server until requests are made to it, by the Metalogix Content Matrix client. For more information about the Metalogix Extensions Web Service, please see the Installing the Metalogix Extensions Web Service page.
Can I use an older version of the Metalogix Extensions Web Service with a newer version of the Metalogix Content Matrix Console?
It is not recommended to use older versions of the Metalogix Extensions Web Service with newer build of Metalogix Content Matrix, but this is possible after build v184.108.40.206. In order to use an older version of the Web Service some configuration changes must be made. To do this, close the Metalogix Content Matrix Console and go to its installation folder (for example, [Drive]:\Program Files (x86)\Metalogix Content Matrix Console - SharePoint Edition). Find the WebServiceConfiguration.xml file, and edit it.
This file will list the default Web Service version number, which can be modified. The format of this entry should be:
<Server Name="default" WebServiceVersion="[Version Number220.127.116.11]" />
Once the old version number is specified, save the XML file and re-open the Metalogix Content Matrix Console.
It is possible to add additional lines to this code to specify server names. In most cases these additional lines only need to be added if connecting to different (or multiple) servers, and these other servers are using a different version of the Metalogix Extensions Web Service. Any number of lines can be added for additional servers. If added, any additional lines will apply the server name and version number to any Web Service connections that are made to the specified server. The default Web Service version number value will be used for all other connections. If connecting to a site that uses Alternate Access Mappings (AAM) that point to a different URL, a separate entry will need to be made for the AAM.
The format for any additional lines is:
<Server Name="http://[ServerName]" WebServiceVersion="18.104.22.168" />
If a newer version of the Metalogix Content Matrix Console is installed the WebServiceConfiguration.xml file will be overwritten, so any manual changes that were made will need to be entered again.