Home > Known Issues
Export to PDFKnown Issues
| Known Issues | Identified in Version |
|---|---|
| AvePoint Opus lets you set retention rules to prune archived data in archival storage. You can configure these at the storage level (Settings > Global Storage Settings) or rule level (Rules > Rule settings), with rule-based settings overriding storage-based ones. However, for data originally archived via Cloud Archiving, Opus cannot apply rule-based retention; you need to set retention rules at the storage level after migrating from Cloud Archiving if you want to prune this data. | February 2025 |
| The Migration from Cloud Archiving job will fail when the content archived by Cloud Archiving is stored in a Box type storage location. Root cause: AvePoint Opus does not support the following storage locations: Box, NetApp AltaVault, and Rackspace Cloud File. | February 2024 |
| When restoring content from an FTP storage location, some history versions of files might fail to be restored due to FTP timeout issue. | February 2024 |
| Migrate stub templates from Cloud Archiving to AvePoint Opus. Create a rule to leave a stub in SharePoint after a document is disposed of, and make sure that the migrated stub template is selected. Run job to process documents in SharePoint and leave a stub for each disposed document. Navigate to SharePoint to view the stub message. In the stub message, tag titles are displayed in English, instead of the language in which the SharePoint site is displayed. | February 2024 |
| Users can change their Exchange mailbox email addresses in Microsoft 365. Once an email address has been changed, the previously scanned email address in AvePoint Opus will be legacy data and cannot be managed by AvePoint Opus anymore. | October 2023 |
| Cloud Records does not support inserting images to email templates via HTML codes. | June 2023 |
| Cloud Records does not support applying terms to system folders within Teams private channels or group team sites. | March 2023 |
| Cloud Records does not support automatically populating a term based on criteria to folders. | March 2023 |
| If you edit a box template to push an existing column to a folder template and a record template, the column inheritance will take effect after the Physical Records Explorer Update job completes as expected. However, after the job completes, the column value fails to be pushed to the folder template and the record template. The same issue exists when you edit a folder template to push an existing column to a record template.Workaround: This issue can be resolved after you save the box template or the folder template again. | July 2020 |
| When you create a site where there are documents that have been declared or checked out or placed on hold, and then create a site level rule to target this specific site and then run a job to delete the site content from SharePoint Online. After the job completes, the documents that have been declared or checked out or placed on hold are skipped in the job as expected. However, a 404 page not found error appears after you access the site.Root Cause: Site home page is stored in the Site Pages Library. For container level rules, content will be disposed of from bottom to top. In the current situation, the site home page is removed together with the Site Pages Library. Thus, users cannot access the site again.Workaround: If you want to delete the site, access the library where the documents that have been declared or checked out or placed on hold exist, and then manually delete the library. Run the job again, the site will be deleted from SharePoint Online. | July 2020 |
| When you create multiple physical folders under a physical box and then place the physical box on hold. The physical box and all folders in the physical box will all be on hold now. If you view details of the hold to see the physical boxes/folders that are currently on the hold, on the details page, the physical box is displayed as expected, however, no physical folders are displayed. Root Cause: This issue occurs because the hold on the physical folders are inherited from their parent physical box. | March 2020 |
| AvePoint Cloud Records now supports displaying the On Loan, Currently Held By, On Hold, and Hold Placed By columns to indicate a physical folder’s loan status and hold status. After upgrading, the original physical folder’s loan status and hold status cannot be kept. | March 2020 |
| Enter a username that does not exist in the system as the Record Owner, and then save the changes. Changes are successfully saved.Root Cause: AvePoint Cloud Records will check whether the entered username exist in the system only when the Send an e-mail notification to Record Owners checkbox is selected. | February 2020 |
| AvePoint Cloud Records cannot automatically enable the Custom Script setting in SharePoint admin center > settings when it runs jobs to manage the OneDrive for Business objects.Workaround: The issue can be solved by manually enabling the Custom Script setting on the SharePoint admin center > settings page, and then run AvePoint Cloud Records jobs. Contact AvePoint Technical Support for assistance. | November 2019 |
| Apply term A to the e-mail A and e-mail B to classify the e-mails. Enable the retention settings on the term A using the retention label A, and then run an Enforce Retention job, therefore the retention label A is applied to the e-mail A and e-mail B. Reclassify the e-mail A using another term where retention settings are disabled, and run an Enforce Retention job again. The retention label A is removed from the e-mail A as expected. However, the e-mail B is also collected in the Job Details.Root Cause: this issue is due to the Exchange Online API limitation that there is a delay when taking actions on the data using the Exchange Online API. | November 2019 |
| If the SharePoint Online site where SharePoint settings are applied is registered using the App Profile authentication method, the Related Records app will fail to be added to the SharePoint Online site. The Related Records feature does not work for the SharePoint Online site.Workaround: This issue can be resolved by manually adding the Related Records app to the SharePoint Online site after the SharePoint Settings job completes. | September 2018 |
| Create a rule where Remove content from SharePoint and destroy and Include related records are selected. Run a disposal job to dispose parent records together with their related child records. When parent records are restored using the Cloud Archiving job, their Related Records column values are also restored. However, the links to their related child records do not work. This is because the related child records are not restored. | September 2018 |
| If a rule is applied to a list level node, the Created By and Last Modified By column values on the Show Report page will be empty.Root Cause: There is no available Client API to retrieve the Created By and Last Modified By column values for list level nodes. | July 2018 |
| If a rule where manual approval is enabled is applied to a list level node, the Content Type, Created By, and Last Modified By column values on the Records for Review page will be empty.Root Cause: There is no available Client API to retrieve the Content Type, Created By, and Last Modified By column values for list level nodes. | July 2018 |
| The NAA Configuration File.xml file does not support the following special characters in the content: < > & ' "Workaround: This issue can be resolved by:● replacing < with <● replacing > with >● replacing & with &● replacing ‘ with '● replacing " with " | May 2018 |
| When using AvePoint Cloud Record rules to tag documents or items using custom metadata, the entered custom column name is case sensitive. However, column names in SharePoint Online are not case sensitive. | 1.0.0 |
| On the SharePoint Settings page, when you configure global settings on an Office 365 group team sites group node, and then click Apply Settings to run a SharePoint Settings job, the SharePoint settings fail to be applied. Root Cause: To apply SharePoint settings to a SharePoint Online node, the Custom Script setting must be enabled for the SharePoint Online node. For self-service created sites or personal sites, the Custom Script setting is disabled by default. Workaround: The issue can be solved by enabling the Custom Script setting on the SharePoint admin center > settings page. For additional assistance contact AvePoint Technical Support. | 1.0.0 |
On this page