Breaking changes from previous Syncplify Server!' versions

This page outlines the significant changes ("breaking changes") introduced in the latest version of the software, as compared to previous versions. It also provides guidance on how to smoothly adapt to these changes when upgrading to the version described in the current documentation.

GetCurrentVFS() is no longer a member of the Session object

In previous versions of Syncplify Server!, to work with the currently active Virtual File System (VFS) from inside a SyncJS script, you'd call:

var currVfs = Session.GetCurrentVFS();
if (currVfs != null) {
    // do something with it
}

In Syncplify Server! V7 GetCurrentVFS() has become a stand-alone function, and is no longer a member of the Session object. You will then need to update all of your scripts using this method, in order to call it like this:

var currVfs = GetCurrentVFS();
if (currVfs != null) {
    // do something with it
}

Read more about this method here.

VFS' ImportFile() and ExportFile() function signature differences

In previous versions of Syncplify Server! the ImportFile() and ExportFile() methods of a VFS object would take a file path and a directory path as arguments, which lead to all kinds of confusion. These functions signatures have now been uniformed as follows:

function ImportFile(localFilePath, targetVfsFilePath: string) respBase;
function ExportFile(vfsFilePath, localFilePath: string) respBase;

Read more on this topic on the specific manual pages for ImportFile and ExportFile.