Restrictions

1. The maximum length of any folder or file name is 128.

2. The maximum total length is 255.

2. No leading or trailing spaces in folder names, file names, or file extensions.

3. Restricted characters in the file name: ¦ | # { } % & t " "" ~ + / \ : * ? < > and the tab key.

4. Prevent Thicket Containers.

A) Folders Only

B) Adds an underscore to the structure otherwise we would prevent it from uploading.

5. Prevent leading tildes in Office 365 only.

6. The max file-size SkySync can upload is 2GB.

7.  SharePoint restricts certain file extensions. Click here for the complete list.

8. If you create a folder within a document library using SkySync, it will be a folder container type.

9. Can only do versioning if versioning is enabled on the library.

10. Managed metadata must be mapped by file if moving between 2 sharepoint instances (contact Portal Architects support for assistance with this procedure).

11. Date preservation only works with SharePoint if you are using author-preservation.

12. The transformation of URLs into SharePoint can sometimes increases the overall URL length which can cause either 400 or 414 URL failures (Spaces are the primary way this can happen).  We recommend the removal of spaces or shrink the URL length to resolve this errors.

13. SkySync does not support Custom Lists or Lists in general and they will not be visible in Navigation

14. SkySync does not support Libraries that have Require Check-out enabled.

15. For additional information on Sharepoint restrictions view this Microsoft Article 

16. Sharepoint does not allow duplicate Enterprise Keywords

17. <> are not allowed in Enterprise Keywords

18. Longest string allowed in an Enterprise Keywords is 255 characters.

Sites

1. Sites do not store files

2. URL of any site can be entered and used as a root

3. You cannot create sites through SkySync; it will create libraries.

4. Metadata is per library, not at the site level.

Common Issues

Error: "The Account 'Joe User' Is Not Authorized to Perform the Requested Operation"

"Additional Behaviors/Symptoms: Error: Not authorized to make that action when creating folders or files in Navigation, "Could not create item:File/Folder name" in Job History

Cause: The account, used to create the SharePoint connector, doesn't have Site Collection access.

Fix: Update the account to have Site Collector access. How to Manage administrators for a site collection

Behavior: SkySync isn't displaying all of my SharePoint library's content.

Cause: This can occur when accessing a SharePoint library that has a custom view (a view other than the default view), as it may impact SkySync's ability to retrieve the content or column data.

Fix: Please ensure the SharePoint library is configured to access content using the default view.

Note: We hope to have this addressed in future versions of SkySync.

Behavior: Newer SharePoint Files are overwritten by Older files during the first run of the job. Even when prefer latest is selected.

Cause: The Sharepoint API does not date support time stamps during the initial run as a result the source is preferred during the first run only.

Fix: If the source has older files than the destination with a copy job it is recommended to use trust mode. In this mode the system will consider all original files to be equal during the initial run.

After the initial run changes made to the files will take precedence as normal and SkySync will preserve the latest or most recent version of the file. 

Error: We're sorry. Please verify your last action and try again.... This error occurs when attempting to impersonate a different user when using a SharePoint before 2013

Cause: This is by design as SkySync was originally made to only be compatible with SharePoint 2013. However, the option will still be visible as the same API is being used.

Fix: User impersonation for Sharepoint before 2013 is not supported, and a new connector for each user would need to be created.

Error: 403 forbidden when creating a SharePoint Connector using OKTA authentication

Cause: This can be caused by the SharePoint Url not being added as a Trusted Origin

Fix: Log into OKTA as an Admin, From the Admin page go to Security>API>Trusted Origins> Add Origin> Check Both Boxes and add the Sharepoint site

Behavior: I am unable to view the Custom Lists on my site in Navigation

Cause: SkySync does not support Lists

Behavior: Root folders and subfolders are created, but there are no documents inside the folders.

Cause: This can occur when the SharePoint Library/Site settings are configured to "Require Check Out".

Fix: Verify that these libraries, or even the site defaults, are NOT set to "Require Check Out". Follow these instructions, but toggle the setting to "No".

Authentication

Variable – Basic, Forms, NTLM, Kerberos, SSO

1. SSO – Okta, All with O365

2. On prem – Okta and ADFS

3. O365 - All SSO

Forms-Based Authentication

When Forms Based Authentication (FBA) is enabled for a SharePoint site, SkySync will always choose FBA over any other authentication method. When attempting an FBA connection, SkySync will make a call to the Authentication.asmx, passing the user credentials which must be from the FBA user list (it cannot be an AD user). Passing an incorrect user will return a password match error so it may not be clear that you have selected a user from the wrong list.

Is User Impersonation Supported?

SharePoint 2013 supports user impersonation through the SharePoint API but SharePoint 2007 and SharePoint 2010 do not.  The option is visible as they share the API but it is not available before 2013. It should be kept in mind that impersonation is for files only, not folders.

Additional articles about his connector