How my external data source fields are mapped to my SharePoint list columns?

The SharePoint Business Data List Connector (BDLC) is used to connect SharePoint lists (no Web Parts) directly to external LOB data.

External data conencted to SharePoint lists

The BDLC automatically creates the list columns required to host your external data source in a SharePoint list. The field names exposed by your select statement are used as column names automatically. But what about the field types and field names?

FIELD TYPES

  • Any numbers, values etc. are mapped to numbers in SharePoint list columns. Please change formatting directly in SharePoint, if required.
  • Any booleans are mapped to SharePoint true/false column types.
  • Any Date/Time fields are mapped to SharePoint data/time column type. Please change formatting directly in SharePoint, if required.
  • Any other field types are mapped to SharePoint text column types. Please change formatting directly in SharePoint, if required.
  • Binary fields (BLOBS etc.) are not supported as this time. Text fields with a default string are created for this type of fields.

FIELD NAMES

SharePoint list column names are automatically created based on data source field names.as delivered by the select statement. The SharePoint column display name is the same as the datasource field name.

Please use the select statement wit aliases directly to give certain columns names, that are different to the source fields, if required, e.g.

SELECT <field name> AS "<new field name>" ...

if your data source supports this type of statement. You can modify the display name of any SharePoint BDLC list column, if required after initial creation manually.

Please note, that special characters in names are processed specifically in SharePoint. There is a 32 character limit for SharePoint internal column names.

You can add additional columns later on after the structure is created (e.g. if the select statement or database structure is changed) using the field name conventions given above.

How to get the existing internal column names from SharePoint? You can do this by using the "Check Mapping" button.

TITLE COLUMN

You should use a single line text field for the Title column in the SharePoint list. If a field name Title is available in the result set, it will be mapped automatically. If the Title field is a primary key, take care about correct internal column name mapping. Don't use the column display name for that.
If no Title field is present, the primary key is used to map the Title column.

ID AND OTHER SYSTEM COLUMNS

Is is not possible to map the item id and other SharePoint system columns like created / modified  etc. by design.

COLUMN PROPERTIES

You can modify column properties after creation of the list structure. Please set single or multi-line text field properties, as required manually. SharePoint allows single line text fields up to 255 characters only.

VIEWS

Please create SharePoint list views without any restrictions to

  • format
  • sort
  • filter
  • group

your data as required.

CALCULATED COLUMNS

You can use calculated columns without any restrictions.

 CHECK MAPPING

Please use the "Check Mapping" button to check the field / column mapping. Every "?" on this screen can indicate a potential mapping problem.

Share this site on Xing
Share this site on Google+
Share this site on LinkedIn

"Please support us to improve our products and solutions. Give us your feedback."

Related Contacts
Frank Daske

Frank Daske

Business Development Manager
+49 (0) 40 28 41 12 - 30
sales@layer2.de

Please note that the 011 exit code must be dialed first for all international calls made from the USA , Canada and Australia.

News

Layer2 Business Data List Connector for SharePoint V5 Released To Close Gaps With External Data Integration

Layer2 has announced V5 of the SharePoint Business Data List Connector that connects almost any external corporate data source with native SharePoint lists and closes many gaps that still exist with SharePoint data integration.

SharePoint External Data Integration Made Easy and Seamless with Layer2 App BDLC V4

Layer2 announced a new version of the Business Data List Connector for SharePoint (BDLC) that connects almost any external enterprise data and processes with native SharePoint lists.
Related Downloads
NoDoc Image

Business Data List Connector PAD File

This XML-based PAD file offers a product description for resellers to download and publish.
PDF Image

Customer Solution Case Study: WealthVest Marketing Benefits From SharePoint Data Integration Using Layer2 Business Data List Connector

"By using the Layer2 Business Data List Connector for SharePoint app we can provide native SharePoint lists as a simple, easy-to-use, and familiar interface to manage mission critical business data."
PDF Image

Flyer: Layer2 Partner Program

Partner with us as a software distributer, reseller or SharePoint, Office 365 or Azure service provider. We are offering a free Partner Program with up to 30% Discount, free NFR licenses etc. Please download for more.
PDF Image

How to connect ANY external data source directly to native SharePoint lists?

Download this step-by-step introduction to the Layer2 Business Data List Connector (BDLC) for SharePoint.
PDF Image

Produktflyer: Business Data List Connector for SharePoint

Productflyer (PDF) in English for download.
PDF Image

Testimonial: How the US Defense Contract Management Agency (DCMA) integrates SharePoint with Oracle using BDLC

"Layer2 Business Data List Connector (BDLC) software provides a powerful mechanism for surfacing external data through lists, and drastically improves platform stability and development cycles."
Related Links

Are you looking for partners in your region?

Please find a local partner here.

BDLC works with NINTEX Workflow 2010 for SharePoint

Start NINTEX Workflows while external data changes.

Layer2 BDLC for SharePoint Community Group @ LinkedIn

​Are you already @ LinkedIn? Please join our group to share your experience.

Sign Up for Layer2 Product Newsletter

We keep you up-to-date about new Layer2 product releases, added features and fixed issues.