Stay up-to-date with hotfixes and new product releases by subscribing to the RSS feed.
- Ability to read not encrypted text from the BDLC configuration list, so now you have the possibility to provision BDLC list entries totally without the use of BDLC API. Be aware that when using passwords to use the SecureStore.
- Writeback whole SharePoint lists to an external datasource. Available through API or Link only. Supports only datasources that can use writeback (no excel, no xml, …). If the datasource side is not empty, existing data could be overwritten when the given primary keys match. Use of IDENTITY or auto incrementation not supported.
- New Odata-Provider. Now supporting OData V1-V4, Atom and Json formats.
- Using a DateTime field as primary field caused an error on writebacks
- Datetime are now handled correctly when using custom edit forms (infopath or aspx)
- Using dates as text value in the connected datasource caused wrong dates due to a mishandling of UTC in SharePoint
- Dates from web services and from the Layer2 SharePoint 2007 List Provider are now handled properly.
- On some occasions a validation failed with message "The connection was not closed. The connection's current state is open."
- Using the "Layer 2 Data Provider for SharePoint (CSOM)", BDLC was unable to synchronize link and person fields properly.
- 2016 IT Preview: While upgrading with the BDLC installer it can run into timeouts. If this happens, remove the BDLC and re-install it.
- When editing a calendar start date and not the end date at the same time on quick view, the end date will be deleted by SharePoint. This delete event will not be routed through to BDLC, so an update with BDLC will bring back the deleted end date. This is a SharePoint bug and not BDLC related.