Release Notes of the 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.17.7.1 (05/2018)

Change

  • The Layer2 Cloud Connector has been updated to use the Microsoft .NET framework 4.6.2 which also supports TLS 1.2 negotiation.
  • Due to the upgrade to .NET framework 4.6.2, Windows Server 2008 SP2 is no longer supported.

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.
  • In some cases, if a connection file was corrupted, it prevented the Backend-Service from starting up.
  • In some cases, the synchronization of SharePoint-Calendars were very slow.
  • Deleting the Metabase folder led to aborted synchronizations.
  • In some cases a SharePoint error "Collection or property has not been initialized" occurred.

Hotfix 7.17.7.1 (uploaded 23/05/2018)

  • On some systems Synchronizations would abort with an error if Dynamic Columns were used.

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).

 

Icon for Product Regsitration - Layer2 leading solutions

Update to current release

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