...
Platforms all have unique features and limitations. DryvIQ’s transfer engine manages these differences between platforms and allows you to configure actions based on Job Policies and Behaviors. Utilize the Platform Comparison tool to see how your integration platforms may interact regarding features and limitations.
...
Maximum file size: 100 GB
Maximum file name path length: 400 characters
Restricted characters in file/folder name include / , | , \ , \\ , / , : , * , ? , < , >
Invalid folder names: _t, _w
Maximum number of files per folder 5000
OneDrive for Business does not allow the following:
Two consecutive periods
Leading or trailing periods and white spaces
Non-printable ASCII characters
For more information on OneDrive for Business, see Microsoft’s official documentation.
Note |
---|
Transferring Microsoft Lists is not supported. |
Connection Pooling
Connections using OAuth 2 authentication may experience bandwidth throttling from Microsoft when using connection pooling.
Impersonation
Impersonation is not supported for SharePoint Online. Impersonation is only supported for OneDrive for Business.
...
Graph API does not support lock event detection without the use of a separate API call, which will slow down change detection. The workaround is to disable native event detection to transfer locks in each job run or to use a soft reset to transfer locks as needed.
Mapping
When creating CSV mapping files for import, the usernames must be lowercase to properly adhere to the search requirements for the connector.
...
SharePoint Online Folder Created Date may experience a discrepancy in timestamps when using CSOM and Batch Mode.
This behavior is a known issue within OneDrive for Business / Office 365.
DryvIQ will attempt to preserve timestamps on folders when using both CSOM and the batch API. However, the behavior of SharePoint Online is to update the folder's modified dates whenever a file is uploaded into it.
As a result, when using CSOM, the timestamps will be preserved when the folder is initially created but then updated after every file that gets uploaded. When using batch API, it preserves the timestamps on the folders after all of the files within the batch are committed. This is the cause for the discrepancy between the two methods.
...