Cloud Drive Mapper (CDM) 3.19 (Pre-release)

Enhancements

• The order of your CDM-mapped drives in the Active drives window will now represent the order in which you’ve configured them in your mapping group in Iris.

  Reference No: 29022

• We’ve intentionally removed all CDM configurations from the config.json file, and we no longer support the ability to make any changes to it unless otherwise instructed by our support team.

  Reference No: 29765

• CDM will now sync changes in real time when an individual user edits a document with autosave enabled. During co-authoring, CDM will sync changes at the next delta refresh interval.

  Reference No: 29866

• You can now specify how you want your Dynamic SharePoint and Direct SharePoint site drives to handle their folder structure. Your choices include allowing CDM to mount the drive with (where sites and subsites are nested) or without (where sites and subsites appear at the root of the drive), preserving site or subsite hierarchy. By default, CDM will honor the site or subsite hierarchy. However, this will not apply to existing mapping groups with Dynamic SharePoint drives.

  Reference No: 32195

• We’ve overhauled how CDM’s Dynamic: SharePoint drive maps your SharePoint environment to a drive letter. This has allowed us to significantly reduce the calls it makes to Microsoft 365 during a delta refresh. Until now, this drive would make a call for every SharePoint site you are a member of while mapping, and then once again after the expiry of the specified cache refresh frequency, which is approximately an average of 3 hours by default. This is no longer the case. However, this has resulted in an expected change in behavior. The drive shows locked SharePoint sites and those without document libraries by default. When you interact with a locked SharePoint site, CDM adds it to a special long-term cache for 5 days. During that period, unlocking a locked SharePoint site will not automatically show in your Dynamic: SharePoint drive. Each site added to the cache has a unique expiry timestamp, meaning CDM will check them randomly and evenly across your SharePoint environment. If you want CDM to respond efficiently to the locking or unlocking of a SharePoint site, we’ve introduced a way to do this. Learn more

  Reference No: 32607

• Unlike OneDrive, which only stores its cache data in your local AppData directory, CDM can now store this information in the AppData directory and a hidden folder within your OneDrive. This dual-location strategy is particularly beneficial in environments with mandatory profiles, no profile solutions, and device-independent or VDI setups. It relies on you logging into your Microsoft 365 account to access your OneDrive, allowing you to seamlessly roam on and off your network and reducing repeated permission checks between CDM and Microsoft 365 to avoid issues like throttling. To ensure this enhancement functions correctly, grant admin consent to CDM after installing version 3.19 by clicking here. Learn more

  Reference No: 32697

• We’ve enhanced how CDM handles file saving from third-party apps. This improvement will also help preserve the version history of such files in the cloud.

  Reference No: 32706

• Until now, inserting a link to an Office document (stored on a CDM-mapped drive) into another Office file would result in Microsoft Office inserting the document’s UNC path in the link. The issue with a UNC path is that it is unique to a specific user’s session and may not work for others. To mitigate this issue, CDM can now replace the UNC path in the link with the CDM-mapped drive’s drive letter so that it remains active when shared with other users. While this enhancement supports all other Office apps as is, you need to ensure that you’re using Microsoft Excel version 2503 or higher for Excel files.

  Reference No: 33134

• CDM now supports the ability to hide sites that are marked as excluded for Dynamic SharePoint and Microsoft Teams drives. This will allow CDM to effectively reduce the possibility of throttling, improve performance, and the user experience. Learn more

  Reference No: 33389

• We’ve optimized CDM’s startup flow to ensure that any changes to drive settings are applied as soon as you restart CDM.

  Reference No: 33615

• You can now change the base path for where the CDM file cache and data reside. The flexibility to store this information at another location from where it is easier to restore during login will enable you to provide a more seamless experience to your users.

  Reference No: 34011