North America: +1 (646) 257-3449
Global: +91-44-2471 7142
Support Hours (M - F) : 9am - 8pm IST (GMT+5:30)
Current Time :  0:00:00 pm IST (GMT+5:30)
SPListX for SharePoint
Home :: Products :: SharePoint :: SPListX for SharePoint

SPListX for SharePoint

7.14
DownloadRequest QuoteBuy Now

Can SPListX be installed and run from a client machine?

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.

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

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.

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.

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 common application data 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 cleanup utility periodically to maintain the task files.

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.

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

Does SPListX support 64-bit platform?

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

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

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.

I notice a difference in the search results in SPListX. Are there any known issues?

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.

Does SPListX work with SharePoint Online in Office 365. How does it work?

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.