The BDLC can close many gaps that still exists with SharePoint external data integration via BDC/BCS out-of-the-box.
This FAQ is about the SharePoint Business Data List Connector (BDLC) product version history. For any questions please use the FAQ Web Form or contact [email protected]
To connect a SharePoint list with a SQL Server table or view using the SharePoint Business Data List Connector (BDLC) you have to add a valid select statement. Some samples are given here.
If a SharePoint List is connected directly with an external data source using the SharePoint Business Data List Connector (BDLC) the BDLC automatically creates the required list columns. But what about field types?
You can use the SharePoint Business Data List Connector (BDLC) to connect Excel as your external data source to a SharePoint list. This FAQ is about how to create a valid selection statement for this.
In the BDLC list settings dialog you can enable or disable background updates only. There are no further settings about timer interval, next run etc. But how to manage these settings?
The SharePoint external list via BCS is a great step forward with data integration. But it's not a native SharePoint list. And that's why it hasn't all list features - as the BDLC list does.
With SharePoint BDLC V1.6 you can update BDLC lists on demand per URL or on page load.
You can simply remove unused columns in your SharePoint BDLC list by deleting it. Missed columns are skipped during updates without causing any problems. Warning: You should not remove columns that host primary keys.
The BDLC can be used to pull data from other SharePoint lists for any reason.
Yes, you can add additional fields after list creation without any restrictions.
SharePoint out-of-the-box can sync some data in Microsoft Exchange to same lists in SharePoint. Connecting a custom SharePoint list to Exchange or Outlook with the BDLC to pull data into this list is a more general approach.
You can connect a custom SharePoint list directly with external data from Oracle database tables or views using the Business Data List Connector (BDLC).
You have to pull the user's / group's ID from the User Information List in the current SharePoint Site Collection into the user / group picker field to reference to a certain user or group.
About using SharePoint BDLC with NTLM Authentication, Basic Authentication, Kerberos and Trust computer for delegation privilege in Active Directory (AD) or explicit credentials.
Using a BDLC list you can add collaboration content to LOB data for example. To prevent users from editing content, that come from the external data source, some or all SharePoint list columns / fields can be set read-only.
You can connect a custom SharePoint list (no Web part) directly with external data from Active Directory, e.g. users or devices, using the SharePoint Business Data List Connector (BDLC).
To connect Microsoft Office 2010 data directly to SharePoint 2007 / WSS 3.0 lists, without Office installed on the server, you have to install the Office 2010 System Driver - Data Connectivity Components.
You can fill SharePoint link columns from external data using the BDLC without any problems, if you follow these steps.
How to configure BDLC to link a SharePoint list to a Microsoft Dynamics NAV 4.0 (Navision) non SQL Server table or query via C/ODBC directly in the list settings dialog without any programming or tools.
BDLC V3.0 finally comes with optional write-back to external data source features. CRUD (Create, Update, Delete) is fully supported for the external data source, if SharePoint list items are created, updated or deleted.
You can use Xtract Universal as a driver, to connect any native SharePoint 2007 / 2010 list directly to SAP data via Business Data List Connector for SharePoint.
First you have to install the appropiate .NET based provider (driver) on application server and web frontend server. Please take care about 32/64-bit: The driver should be the same as your SharePoint currently runs.
You can connect any SharePoint list directly with Microsoft Exchange Server data, e.g. contacts, tasks, events, inbox and other folders using the BDLC and a simple middleware driver.
You have to create your ODBC data source and access it as SharePoint list via BDLC. Here is a step-by-step sample.
You can connect a native SharePoint list (no Web Part / BDC / BCS) directly with external data from AS400 database tables. Information how it works is found here.
You can connect a SharePoint list with another SharePoint list (at the same or at another installation) to pull the data and keep up-to-date with background update.
How to connect native SharePoint lists via OLEDB directly to Active Directory to create a phone book application with search within 10 minutes.
The Business Data List Connector allows data replication between SQL tables and SharePoint lists both directions with full CRUD (create, update, delete) support. GUIDs can be used as primary keys for that.
The SharePoint BDLC can be used to connect any external data source to a native SharePoint list, e.g. contacts, tasks, events or custom items. The SharePoint Secure Store can be used to store all security relevant information safely.
Specifications of the CSOM-based Layer2 Data Provider for SharePoint to connect to SharePoint 2010 / 2013 or SharePoint Online / Office 365 via ADO.NET.
The SharePoint BDLC can be used to connect almost any external data source to native SharePoint lists, even external XML data, file-based or based on web requests. This FAQ gives the full specifications of the Layer2 Data Provider for XML.
You can synchronize external XML data e.g. file or web requests with native SharePoint lists using the Layer2 Business Data List Connector.
Often there are issues to connect external data via web services (e.g. CSOM, OData) using SSL/HTTPS from inside SharePoint. This FAQ shows how to solve these general SharePoint (not BDLC related) issue.
The Business Data List Connector can be used to connect almost any external data source to native SharePoint lists, e.g. external OData via web requests. This FAQ gives the full specifications of the Layer2 Data Provider for OData.
The Layer2 BDLC is made for large scale external data integration scenarios as well and can manage more than 200.000 external items without any issues.
How to map existing SQL foreign key table relationships to SharePoint lookups using Layer2 BDLC and workflows?
You can connect and synchronize native SharePoint lists with SAP data via NetWeaver, OData and the Layer2 Business Data List Connector codeless in just minutes.
While external data integration and synchronization of SharePoint lists can be done codeless in just minutes via Layer2 BDLC, it takes a littele bit more time to add your specific business logic.
To successfully authenticate your external data source using integrated authentication in a claims-based SharePoint environment, the Claims to Windows Token Service should be up and running. You have to use the SharePoint Secure Store.
With BDLC 2.0 you can connect any existing SharePoint list to external data, e.g. contacts, tasks etc.
BDLC V1.6 comes with greatly improved field / column mapping features.
SharePoint BDLC 1.5 comes with highly improved support for much more external data sources.