1.

Can SPListX be installed and run from a client machine?

Yes, SPListX can be installed and run from a Windows XP or Windows Vista desktop (client workstation) with .NET Framework 2.0 or later.

2.

Can I connect to a remote SharePoint server within my local network through SPListX?

Yes, you can connect to a 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.

3.

Does SPListX support a batch file for export instead of setting up the export task through the user interface?

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.

4.

Can I selectively export files from SharePoint library?

Yes, files from SharePoint library can be selectively exported to the file system.

5.

Can I export all versions of a file from SharePoint library?

Yes, you can export all / specified versions / latest version of file from SharePoint library to file system.

6.

Can I export documents and folders from multiple libraries?

SPListX allows you to export folders and files from multiple libraries in a single export session.

7.

Can I export a folder and all its contents, including sub-folders, to File System?

Yes, you can export a folder and all its contents, including sub-folders, to File System.

8.

Can I view only the file list of a list and their associated column values?

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.

9.

Where are the versions saved when I export files to the file system location?

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.

10.

The application error log file SPListXErrorLog.txt in the SPListX application path is gradually increasing in size. Can I delete it?

Yes, you may delete this error log file. SPListX generates an error log file in the Log folder in the application path (<Application Data Folder>\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 clean-up utility periodically to maintain the task related files.

11.

What is the required structure for the batch descriptor file?

Refer to the relevant sections in the application help file for more information.

12.

Can I retain Created date and Last Modified date of a file when exporting to file system?

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.

13.

What permissions are required in SharePoint for SPListX to export files from a library?

For the export task to run as expected, the given user credential must have at least Read permissions in the source library.

14.

What are the limitations in the evaluation copy?

SPList Export for SharePoint 2007 evaluation copy has a 15-day evaluation period and 250 items export limit, whichever comes first.

15.

Can SPList Export for SharePoint 2007 export tasks be invoked from the command line or scheduled?

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.

16.

Does SPList Export for SharePoint 2007 support 64-bit platform?

Yes, SPListX supports both Windows Server 2003 (32-bit and 64-bit) and Windows Server 2008 (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).

17.

Can SPListX export list item attachments?

Yes, you can export list metadata along with the file attachments to the Windows file system.

18.

Can I selectively export list items and metadata from a SharePoint list?

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).

19.

Can I export all versions of list items metadata from a SharePoint list?

Yes, you can export all / specified versions / latest version of list items metadata from SharePoint list to metadata file.

20.

Where are the attachments saved when I export attachments to the file system location?

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 "NewYork" and id is 2, then a folder with name 'Attachment_NewYork_2' will be created in the destination folder and the list item attachments will be exported to this sub-folder. 

21.

Can I export list items based on SharePoint search?

Yes, SPListX supports exporting list items / documents (metadata and file attachments) based on SharePoint Search feature.

22.

Where are the search results saved when I export to the file system location?

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 <Content Type>, then a folder with the corresponding list item <Content Type> name will be created in the destination folder and the matching results will be exported to this sub-folder.

23.

What are the authentication methods that SPListX supports?

The current version of SPListX supports Windows authentication and Forms authentication methods only. Moreover, SPListX will automatically detect the configured authentication in destination SharePoint site and connect it by initiating respective authorization process against SharePoint site.

24.

Can I use FQDN based user credential in SPListX?

Yes, SPListX supports both NetBIOS conventions and FQDN conventions to connect to SharePoint site.

25.

Is there a known issue in Form Authentication affect my search results in SPListX? 

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.