SharePoint Products

compelling add-ons for SharePoint

CopyMove 2010 - V2.6.0 released
Monday, January 19, 2015

Once again it has been about six months since the last public release of CopyMove 2010. But we have during this time continued to implement improvements and hotfixes on request from our users. The time has now come to wrap it all up into a new public release here on the product web site. The changes since V2.5.0 include:

  • Added support for moving items on hold - but only for site collection administrators.
  • Added validation check to fail early when users attempt to copy/move folders into document sets. This is not supported by SharePoint 2010 and would before cause CopyMove to fail unexpectedly.
  • Added support for configuring the maximum number of recent folders to show in the target selection tree. The new setting can for now only be configured through the PowerShell cmdlet Set-CopyMoveSettings and the configuration XML element named <MaxRecentFolders>. The default value is 20.
  • Added the PowerShell cmdlet Remove-CopyMoveSettings to support scripted removal of CopyMove settings from site collections.
  • Added protection for Cross-Site Request Forgery (CSRF).
  • Added support for disabling SharePoint item events firing in the CopyMove worker thread. Just disable them (SPItemEventReceiver.EventFiringEnabled = false) in the client thread and CopyMove will also disable them in the worker thread.
  • Added new Items array property to the CopyMoveResult API object. It reveals the id and url of all target items that were copied, moved or imported by the CopyMove transaction.
  • Added Japanese translation of the user interface.
  • Improved the PowerShell cmdlet Set-CopyMoveSettings to support setting individual settings directly.
  • Updated the WCF Sample in the product download to support SSL and other SharePoint credentials than the current Windows user.
  • Disabled trimming of duplicates when quering sites by wildcard for the target selection tree.
  • Deprecated the CopyMoveItemTransaction.Recursive property in the API. Instead, use the CopyMoveTransaction.IncludeFolders property.
  • Fixed error when copying MS Office documents on hold.
  • Fixed issue where Document IDs were not retained when copying/moving documents to a document library configured for auto declaration of records.
  • Fixed incorrect error message 'No items found' that showed when other errors were identified for the selected item(s).
  • Fixed issue where read-only users could not copy documents with no major version.
  • Fixed permissions issue where users could use the CopyMove import function even if CopyMove permission levels were enabled and the import permission was not granted.
  • Fixed issue where the Recent Folders node in the target selection tree would show folders from incompatible target lists.
  • Fixed error 'Error importing folder [url] because the parent folder [url] does not exist', which was triggered when copying/moving items in nested folders using wildcards through PowerShell or through the API.
  • Fixed issue where the CopyMove target selection dialog could not query site collections from a URL wildcard pattern like https://host/sites/*. This problem surfaced when SharePoint 2010 consumed a Search Service Application from SharePoint 2013.
  • Fixed issue where the version history of folder items were not preserved.
  • Suppressed the error 'The URI scheme is not valid' that showed when the list of admin defined sites in the selection tree.

The new version of CopyMove 2010 is available for download from the CopyMove 2010 Download page.​​​​​​​​