| |
| Q.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.
|
| Top |
|
Q.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.
|
|
Top |
| Q.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.
|
| Top |
|
Q.4. |
Can I selectively export files from SharePoint library?
|
|
Yes, files from SharePoint library can be selectively exported to
the file system.
|
|
Top |
|
Q.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.
|
| Top |
|
Q.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.
|
| Top |
|
Q.7. |
Can I export a folder and all its contents, including sub-folders, to a
File System?
|
|
Yes, you can export a folder and all its contents, including sub-folders, to a File System.
|
| Top |
|
Q.8. |
Can I view only the file list of a library 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 library. When you run such a task, SPListX generates a file (CSV / XLS / MDB based
on user selection) that will contain the list of folders / files and their associated column
values.
|
| Top |
|
Q.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.
|
| Top |
|
Q.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 (C:\Program Files\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.
|
| Top |
|
Q.11. |
What is the required structure for the batch descriptor file?
|
|
Refer to the relevant sections in the application help file for more information.
|
| Top |
|
Q.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.
|
| Top |
|
Q.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.
|
| Top |
|
Q.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.
|
|
Top |
|
Q.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.
|
|
Top |
|
Q.16. |
Does SPList Export for SharePoint 2007 support Windows Server 2003 64-bit platform?
|
|
Yes, SPListX supports Windows Server 2003 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).
|
|
Top |
