We have released Dockit 365 Archiver v1.0.6432 with certain enhancements and bug fixes recently. Since majority of the changes in this new version are based on the feedback from our customer, we hope that this update will be very useful for all of our customers.
These are the enhancements and bug fixes included in this new version:
- Excluded the timestamp folder creation.
- Existing files in target with same name as files in source, will be skipped from export.
- Changes to the metadata file.
- Fixed the mismatch of Modified Date value in SharePoint and metadata file.
- Library without contents will not be exported.
- Created Date and Modified Date are retained in file system.
- Removed additional files creation.
- Fix for “The request failed with HTTP status 503: Service Unavailable.” error that occurred due to SharePoint throttling.
Excluded the timestamp folder creation:
In the previous versions of Dockit 365 Archiver product, a timestamp folder will be created in the export location when archive job initiates the process. The SharePoint contents will then be exported underneath the timestamp folder.
In case of automation, users are not interested in time stamp folder creation, when exporting SharePoint contents. This is mainly because the automation process will follow a definite algorithm to read the exported contents and perform multiple actions, like, migrate them to a new repository, doing data management operations.
Hence, in accordance with the customer needs, this behavior has been changed in the new version and thus SharePoint contents will be directly exported in the given export location without creating the timestamp folder.
Existing files with same name as files in source, will be skipped from export:
With the removal of timestamp folder creation in this version, we have modified the default behavior of handling file export for already existing files in target archive location.
If a file with same name already available in target location, the application will now skip the file from export, instead of overwriting the already existing file.
By this way, users who are unaware of this change will not lead to the risk of losing the previously archived content by the application.
Changes to the metadata file:
Based on the requests from one of our customers, we have included a few columns in the metadata file, as stated below:
‘Source Path’ – Absolute URL of the source SharePoint file or folder that is exported.
‘Destination Path’ – Absolute file system path of the file or folder as exported in the archive location.
‘Content Type’ – Display name of the content type associated with each file / folder that is exported, in addition to “Content Type ID” column.
Fixed the mismatch of Modified Date value in SharePoint and metadata file:
The earlier versions of Dockit 365 Archiver exports the values of ‘Modified Date’ column for files and folders, advanced by 1 hour from the actual value in SharePoint, for each file version (except for the latest one).
Library without contents will not be exported:
If a library in source SharePoint does not contain any file/folder, then the library will not be exported in the given target archive location. Previously, an empty folder will be created in destination with the same name as that of empty library in SharePoint.
Created Date and Modified Date are retained in file system:
Since Dockit 365 Archiver product has been originally designed for SharePoint archive and restore business requirement, we have left the Created Date and Modified Date of the files and folders to get the export date and time in file system.
With range of customers using the product for simple export to complete archival of their SharePoint repository, we have started receiving feedback from them to retain the original created date and modified date of files and folders as in source SharePoint, during export.
In order to adhere to industry standards and our own SPListX for SharePoint product behavior, we have decided to export files and folders with their original dates in source SharePoint, by default.
Removed additional files creation:
Like in the previous change, with SharePoint archive and restore functionality in mind, Dockit 365 Archiver product created additional dependent metadata files. These files, apart from the primary Excel metadata file that contains the file entries and their associated metadata, is used by the application to import the files back to different SharePoint environment.
We have removed the file creation temporarily, though we do have plans to include the restore (import) provision in the product again.
Fix for “The request failed with HTTP status 503: Service Unavailable.” error that occurred due to SharePoint throttling:
SharePoint processes the incoming requests initiated by end users via browser or custom code or script and serves them.
SharePoint enforces throttling to limit the number of concurrent requests to prevent overuse of resources and thereby maintain optimal performance and reliability of the SharePoint service.
Whenever the number of incoming SharePoint requests exceed the maximum allowed throttling limit, then SharePoint provides limited response or even blocks the response. Due to this, Dockit 365 Archiver might report ‘The request failed with HTTP status 503: Service Unavailable.’ error that it encounters from SharePoint.
Previously, the application will skip that file from export and proceed with the next file. We have modified our application to overcome this condition by retrying to export the file to stated archive location.
This post first appeared on SharePoint Migration & Office 365 Reporting Management Solutions, please read the originial post: here