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).
More features to make your work even easier.
New
-
Now you can authenticate against Microsoft Dynamics CRM with your own custom app registration using the authentication method ModernCrmCustomApp.Thus, Allowing you to have full control
over your app permissions when accessing your Microsoft Dynamics CRM with the Layer2 Cloud Connector.
Find more information about how-to use this new authentication method in our Layer2 Cloud Connector's User Documentation.
At the same time, feel free to explore our solutions page for the many CRM/ERP systems supported by the Layer2 Cloud Connector CRM/ERP Solutions.
Changes
-
We are happy to announce that a huge improvement has been made to our Layer2 OData Provider used by different systems, e.g.: Microsoft Dynamics CRM.
Now the reading time of the records to be synchronised by the Layer2 OData Provider is much more faster, allowing the Layer2 OData Provider to read 500k records in just 8 minutes(depending on network bandwidth). Once the records are read, the Layer2 Cloud Connector can start the synchronisation process.
With this huge improvement the synchronisation time is reduced considerably, since the records' read process can take minutes instead of hours.
Try it out with our Layer2 OData Microsoft Graph how-to guide, and test how fast does the Layer2 Cloud Connector synchronises your data. -
If the synchronisation to SharePoint is being throttled, now the Layer2 Cloud Connector will retry the request accordingly to the time provided by the SharePoint HTTP 'retry-after' header.
This change improves the Layer2 Cloud Connector performance when dealing with SharePoint throttling errors.
Get your Layer2 Cloud Connector copy here and try out our Layer2 Provider for SharePoint On Premises and Online. - Now the Layer2 Cloud Connector is able to read and write to custom fields that have the same name as any internal list item properties, e.g. "DisplayName".
Fixes
- An error caused by parsing a SharePoint List or Library URL under a subsite named 'Forms' has been fixed.
- If a file cannot be synchronised with the Layer2 Filesystem Provider due to unsupported characters in path, the file path with the unsupported characters will be shown in the error message.
