...

Version 5.

...

4 Release Notes

Version: 5.34.30.36623709
Release Date: March 2April 20, 2023 

DryvIQ Migrate version 5.3.3 4 was available on March 2April 20, 2023. This is a maintenance release that focuses on enhancements and bug fixes. Learn more about the release below. For detailed information about individual items, refer to the DryvIQ Platform Documentation Center.

New Features and Enhancements

• The Microsoft SharePoint connections (Microsoft Office 365, Microsoft OneDrive for Business, and Microsoft Teams) were updated to provide the SourceType field Microsoft now requires when calling the Migration API. Please refer to Microsoft’s What’s new in the Migration API documentation for more information about the new required field.

• The Dashboard page was updated to remove links to outdated blog posts.

Fixes

• The ShareFile connector was updated to fix an issue where a job configured to only transfer the latest version of a file was skipping files and only transferring directories.

• When a Sharepoint Migration API batch job encounters a “JobError” or “JobFatalError,” all items in that batch job will be marked as retry.

• The “Move” job type now consistently deletes items after they have been migrated.

• File updates in OneDrive were being detected as move events in a sync job, resulting in files being transferred repeatedly. This issue has been resolved.

• Sync jobs between Box and NFS will no longer produce a "Collection was modified; enumeration operation may not execute" errorDryvIQ updated our Microsoft connectors to use Microsoft’s preferred Delta API, which allows DryvIQ to perform Migration delta runs more efficiently.

Fixes

• Updates were made to prevent jobs from getting stuck in a queued status due to a “Quartz.JobPersistenceException.”

• Permissions for disinherited folders will be reapplied when performing a permissions reset on a job from Box to Microsoft Office 365.

• Duplicated jobs no longer ignore the version setting from the original job.

• Updates were made to prevent an “object reference error” when resolving export links between Google Shared Drives and Microsoft OneDrive.

• If an impersonated user is disabled in Box when it is set as the source connection, the Job status will be set to “Failed to start” rather than “Idle.”

• Updates were made to logging to add a new "Fatal" job execution status. Jobs that encounter this error will have a “Failed” status in the user interface.