Dockit Archiver v8.0.6633 Released!

The new version of Dockit Archiver has been released with certain feature enhancements and bug fixes recently. We hope this new version will be a useful update for our customers. These are the bug fixes and enhancements in this new version:

Improvements:

  • Make use of RPC call to get the original ASPX server page from SharePoint, instead of giving the rendered outcome of the same.
  • Improvements to pre-calculate the actual size of the attachments, instead of downloading the attachments and adding downloaded size later.
  • Exports recycle bin information in site level.

Bug fixes:

  • Previously, if we select the “Items inactive since / older than” option without providing any input, it throws error message. Then, if we select any other option (e.g., Archive everything) and click on the navigation button, it goes to second option and throws error message to provide input.
  • Unable to export to shared network locations. If we double click on the domain name, it gets cleared. It works, if we provide the shared folder path directly.
  • “Dynamic View” condition shows blank when the user changes the property name and click on OK button.

Exporting recycle bin information in site level.
The released version of Dockit Archiver exports/archives the Recycle Bin information (i.e., exports the information only in metadata file). It will not archive those contents from SharePoint. It is applicable for both Export and Archive modules. Also, it exports both site and site collection level recycle bin (including secondary storage information).

Below is the screenshot showing the Recycle Bin information in metadata file:

If we select the “Items inactive since / older than” option without providing any input, it throws error message. Then, if we select any other option (e.g., Archive everything) and click on the navigation button, it goes to second option and throws error message to provide input.

If we choose Items inactive since/older than option without providing any values and try to navigate to next step, it will throw an error message. This validation is correct. However, after that, if we choose another option (say, Archive everything), and try to navigate using navigation button, it goes to the second option and throws error message.

In the above case, it will proceed without throwing error message sometimes, but the navigation button will not work at that time. This has been fixed in this version.

Below is the screenshot showing the error message, when trying to navigate using navigation button:

Unable to export to the shared network locations. If we double click on the domain name, it gets cleared. It works, if we provide the shared folder path directly.

The previous version of Dockit Archiver failed to export/archive contents to network share locations as target, but can export if we provide the exact shared folder path directly in the application. If we try to open the network share (domain name) by double clicking on it, it will get disappeared and can’t be viewed. Now, this has been fixed.

“Dynamic View” condition shows blank when the user changes the property name and click on OK button.

The Dynamic View filter condition will be displayed empty, if we change the “Property” field and click on OK button. This has been fixed.

Below is the screenshot showing the blank screen in “Dynamic View” filter:

Make use of RPC call to get the original ASPX server page from SharePoint, instead of giving the rendered outcome of the same.

The previous version Dockit Archiver exports aspx pages as html file directly without giving the exact aspx page format. In this version, exact outcome will be retrieved by RPC calls and will export the aspx pages in the correct format.

Improvements to pre-calculate the actual size of the attachments, instead of downloading the attachments and adding downloaded size later.

Previously, Dockit Archiver exports the attachments initially and then calculates its size. In this version, the exact size of the attachments in SharePoint lists will be pre-calculated with the help of REST API instead of adding the attachments size later.