Release Notes of Layer2 Cloud Connector

The Layer2 Cloud Connector can be used to connect and sync various enterprise data sources codeless, on-premises and in the cloud, especially with Microsoft SharePoint, Office 365, Exchange and Dynamics CRM/ERP. Please find the release notes and version history for the Layer2 Cloud Connector here. You can subscribe to the RSS feed (works best with Firefox) to stay up-to-date in Firefox or NewsFlow. If you have questions or issues, please join the Layer2 Cloud Connector Community at LinkedIn or contact [email protected] directly.

Release Notes - Layer2 Cloud Connector
V7.16.4.0 (04/2018)

Change

  • Error messages are now shortened on the user interface to provide a cleaner view.

Fixes

  • Version 7.11 introduced a bug where in some rare cases where SharePoint was used as source in uni- and bidirectional synchronizations, unexpected deletes might happen. This bug was fixed with version 7.16. We recommend to update for all affected customers.
  • The SharePoint error due to exceeding the maximum size of a request was not handled correctly in some cases. The processing of SharePoint requests was optimized.
  • When a synchronization targeted a folder of a SharePoint library, "Verify connection string" and "Preview Data" read all items, which led to an apparent application crash in case there were a lot of files in it.
  • In some cases when file path is mapped, an error occurred that it already has been mapped.
  • Automated OData service version detection did not work for Project Server 2013.

Ready to go next steps

Icon for Release Notes - Layer2 leading solutions

Subscribe to release notes

Subscribe to the Layer2 Cloud Connector release notes as RSS feed to stay up-to-date with hotfixes and new product releases. (Firefox is recommended).

 

Subscribe now
Layer2 leading solutions product regsitration icon: a grey square with a big orange pen symbol.

Update to current release

Register to download the current product release here, or use your personal download link in your first registration mail instead.

 

Update now