Yes, SPListX can be installed and run from a Windows 8 / 7 desktop (client workstation) with .NET Framework 4.5 or higher.
Note: For connecting to SharePoint Online in Office 365, Windows 7 with the latest service pack and .NET Framework 4.5 or higher is recommended.
Yes, you can connect to a Microsoft SharePoint Foundation 2013 / Microsoft SharePoint Server 2013 / Microsoft SharePoint Foundation 2010 / Microsoft SharePoint Server 2010 / Microsoft SharePoint Online / Microsoft Office SharePoint Server 2007 / Windows SharePoint Services v3.0 and Microsoft SharePoint Portal Server 2003 / Windows SharePoint Services 2.0 in your local network through SPListX by specifying the required credentials to connect the remote SharePoint server.
Yes, the current version of SPListX support batch documents export from a batch descriptor file. You can create a task of Export files and metadata using a batch descriptor file type, and specify some of the task settings and run.
Yes, files from SharePoint library can be selectively exported to the file system.
Yes, you can export all / major versions / specified versions / latest version of file from SharePoint library to file system.
SPListX allows you to export folders and files from multiple libraries in a single export session.
Yes, you can export a folder and all its contents, including sub-folders, to File System.
You can create a task that exports only the metadata column values for each folder and / or in the SharePoint list. When you run such a task, SPListX generates a file (CSV / XLS / MDB/XML based on user selection) that will contain the list of folders / list items and their associated column values.
When exporting files to a File System with version history, SPListX creates a sub-folder with the name specified by the user (in SPListX task wizard) appended with the version number and exports document version into the respective version folder.
For example: If version folder name specified by the user is ‘Version’ and the actual version number of file being exported is 10, then a folder with name ‘Version10’ will be created in the destination folder and 10th version of the file will be exported to this version sub-folder. The latest version of a file will be exported to the respective version folder depending on its version number.
Yes, you may delete this error log file. SPListX generates an error log file in the Log folder in the common application data path (\SPListX). The error log file tends to increase in size over a period of time especially if the application meets with frequent error conditions. The application does an “append” to the error log each time it runs. This is required for diagnostic purposes during trouble shooting. You may delete the error log file periodically. For each export task, SPListX creates a task folder (same name as task name) and the error log file is stored in the respective task folder. You can use SPListX’s cleanup utility periodically to maintain the task files.
Refer to the relevant sections in the application help file for more information.
Yes, SPListX retains Created date and Last Modified date of a file while exporting to Windows file system. Specify these metadata options in the Export Task Wizard. If the given destination path is NTFS formatted file system, both the date fields – Created date and Last Modified date will be retained as in the source file. However, if the given destination path is a FAT32 formatted file system, Last Modified date alone will be retained.
For the export task to run as expected, the given user credential must have at least Read permissions in the source library.
Yes, you can invoke SPListX export tasks from either DOS command prompt or Windows Scheduler anytime after an export task has been created using SPListX’s export task wizard. Please refer to the relevant sections in the application help file for more information.
Yes, SPListX supports both 32-bit and 64-bit platforms. You can use same setup file to install SPListX main application in both architectures (32-bit or 64-bit platform).
Yes, you can export list metadata along with the file attachments to the Windows file system.
Yes, you can specify the list items to be exported using a batch file or browse through SPListX explorer to select the items to export (with or without file attachments).
Yes, you can export all / major versions / specified versions / latest version of list items metadata from SharePoint list to metadata file.
When exporting attachments to a File System, SPListX creates a sub-folder with the name specified by the user (in SPListX task wizard).
For example: If attachment folder name specified by the user is ‘Attachment’ and the name of the list item is “New York” and id is 2, then a folder with name ‘Attachment_New York_2’ will be created in the destination folder and the list item attachments will be exported to this sub-folder.
When exporting search results to a file system, SPListX creates a sub-folder with the name specified by the user (in SPListX task wizard). For example: If search folder name specified by the user is , then a folder with the corresponding list item name will be created in the destination folder and the matching results will be exported to this sub-folder.
The current version of SPListX supports Windows authentication, Forms authentication and Claims based authentication methods.
Yes, SPListX supports both NetBIOS and FQDN conventions to connect to SharePoint site.
SPListX executes a search query using built-in Search Web Service and exports the items retrieved from the search results. In case you receive zero results (no results retrieved) when you know for certain that there matching results in SharePoint, you may be required to apply the latest software updates service packs. We have noticed that SharePoint 2007 SP1 may be unable to serve the required search results through Search Web Service. In such cases, we highly recommend you to keep your SharePoint environment up-to-date with the latest versions of the software.
Yes, SPListX supports SharePoint Online in Office 365 seamlessly. SPListX supports both Cloud Identity and Federated Identity to connect to Office 365 based SharePoint sites. There is no feature restriction or limitation in SPListX to export contents from Online SharePoint sites.
You can provide the cloud identity user name and password using the option “Use the following credential to connect to SharePoint” available in the export task wizard.
To use federated identity, select “Use Web Single Sign-on credential to connect to SharePoint” option provided in the export task wizard. Please read the help document for more information.
I found Dockit product through SharePoint.com and found it extremely useful. We used Dockit to import hundreds of documents into SPS. Users were in desperate need for them but refused to take the time to upload them. Dockit saved us the upload time, and more importantly, made the information available in a timely fashion. Small issues were worked out quickly by a capable and dedicated customer support staff.
We find that Dockit is an extremely valuable tool for migrating intranet content to SharePoint Portal Server. When you are faced a large number of documents to migrate each of which has to be populated with metadata, Dockit reduces considerably the effort involved in publishing information. Typically it reduces the time a user has to spend per document by 75%, by enabling documents to be published in batch mode rather than real time through the standard SPS interface.
The Dockit application proved extremely useful for importing large numbers of files and folders quickly and easily into SharePoint. Previously, we were having to import files individually, but through using Dockit we were able to deal with huge directories in a fraction of the time that it would have taken. An excellent tool, really glad we found it.
We used Dockit to import over a thousand engineering documents, preserving the folder structure. It was simple to use and saved us a lot of time.