No credit card required. Register, download and try as long as you want. It's all free.
Known Issues & Workaround Faq for tHe Layer2 Business Data List Connector
The Layer2 Business Data List Connector can close many gaps that still exist with SharePoint on-premises standard external data integration. Find answers to frequently asked questions specifically regarding known issues and possible workarounds.
Explore frequently asked questions by topics.
The Layer2 Business Data List Connector for SharePoint (BDLC) solves many issues that still exist with Microsoft SharePoint out-of-the-box external data integration. It makes it as easy as possible to connect native SharePoint lists to almost any external data source, codeless and bi-directional. All SharePoint list features are available for the connected list. The following FAQ is about BDLC authentication options using SharePoint 2013.
The Layer2 Business Data List Connector for SharePoint can be used to connect almost any external data source to native SharePoint lists, e.g. SQL, ERP/CRM, OData etc. It is made for large scale external data integration scenarios as well and can manage more than 200.000 external items without any issues. It helps to overcome the SharePoint limitations with out-of-the-box data integration using data synchronization.
On a 64-Bit SharePoint system you will normally get the "The 'Microsoft.ACE.OLEDB.12.0' provider is not registered on the local machine." message if you try to connect to Office data like Excel or Access or SQL Server via OLEDB. That's because no 64-Bit MDAC driver is installed by default. To connect Microsoft Office 2010 and 2013 data directly to SharePoint lists, without Office installed on the server, you have to install the Office System Driver - Data Connectivity Components. If installed you can connect custom lists directly to Access, Excel or other Office data using the Layer2 Business Data List Connector for SharePoint (BDLC).
The Business Data List Connector for SharePoint connects almost any on-premise or cloud-based data source, e.g. ODBC, OLEDB, OData, Microsoft .NET based providers, Files (Excel, XML, CSV), SQL databases like SQL Server, Oracle, MySQL, IBM DB2, IBM AS/400, IBM Informix, Notes, SharePoint, Exchange, Active Directory, Navision, SAP and many more directly to native SharePoint lists - in just minutes without any programming. But often there are issues to connect via web services (e.g. CSOM, OData) using SSL/HTTPS. This FAQ shows how to solve these general SharePoint (not BDLC related) issue.
The Layer2 Business Data List Connector for SharePoint solves many issues that still exist with SharePoint out-of-the-box external data integration. It makes it as easy as possible to connect native SharePoint lists to almost any external data source, codeless and bi-directional. All native SharePoint list features are available for the connected list.
You can use the SharePoint Business Data List Connector BDLC to pull and update external data from almost any external LOB data sources to custom SharePoint lists (no web parts). But how to pull link data (URLs) into SharePoint link columns?
Our support team always works to provide quick and proper solutions for issues that occur while using the Layer2 Business Data List Connector (BDLC). For the best results, we need detailed information about the BDLC list configuration. The log files, especially those created with the HIGH log mode, give us the information we need to solve your issue and are of far better use for us than any screenshots could be.
You can easily integrate almost any external data source with native SharePoint lists using the Layer2 Business Data List Connector, especially SQL tables or queries. But how to map existing SQL foreign key table relationships to SharePoint lookups? See below for a simple workflow-based approach.
READY FOR THE NEXT STEPS?
