With every new version of SharePoint, Microsoft is improving the Business Connectivity space of the product. As with any product, expectations grow with progressive versions. New versions do not always fulfill the expectations. Here are a few things that are changing in SP 2013 from SP2010 and MOSS 2007:
SharePoint 2013
|
SharePoint 2010
|
MOSS 2007
|
BCS included in Office 13 apps
|
NA
|
NA
|
External Data sources can be:
|
External Data sources can be:
|
External Data Sources can be:
|
BDC Models for OData are created using Visual Studio only. BDC Models for the rest are through SPDesigner
|
BDC Models are defined through SPDesigner / Visual Studio
|
Manual definition of BDC Metadata XML file
|
Event listeners for External Data have been introduced.
This enables SharePoint users and custom code to receive notifications of events that occur in the external system.
|
Notifications not supported
|
Notifications not supported
|
Subscription based data retrieval from external systems is introduced.
The developers can target a particular entity in the external system, such as the Stock entity, and receive notifications about events that are published on that entity. This enables developers to write custom code for external lists that trigger SharePoint events when data is changed - e.g: alert an user, start a workflow
|
Subscriptions not supported
|
Subscriptions not supported
|
BDC models can be scoped to apps for SharePoint, with an option to store connection information in Secure Store, isolated from the model for manageability and security reasons
|
No concept of Apps
|
No concept of Apps
|
Managing the result set is now the responsibility of the external system e.g. Paging, filtering, and sorting of the external list data needs to be taken care by the source system before it is sent to SharePoint. The claim is that this would improve the performance of external lists
|
Filtering needs to be defined in the External Content Type definition
Sorting is done on the entire result set within SharePoint
Paging is managed in a roundabout way by using a filter
|
Methods, which contain the T-SQL or Web service methods that retrieve the entity data. Entities can contain multiple methods and can optionally have parameters and filters defined that Business Data Catalog users can use to filter results
|
By defining data source filter on BDC model, the filtering is expected to happen at source side
|
Filtering needs to be defined in the External Content Type definition
|
Filtering is to be specified in T-SQL / Web Service method parameters
|
Similar to filters, sorting can also be configured to happen at source by specifying in the BDC model. This sorting is expected to happen on the external source
|
Sorting needs to be managed in a roundabout way by using a filter
|
Sorting is to be specified in T-SQL / Web Service method parameters
|
External Lists can be exported to Excel with the following limitations:
|
No ability to Export to Excel, Create Visio Diagram, Open with Access or Open with Project
|
No ability to Export to Excel, Create Visio Diagram, Open with Access or Open with Project
|
External Data Sources for SharePoint online include the following:
|
External Data Sources for SharePoint online supports only WCF connections
|
Not Supported
|
REST APIs for apps (web and mobile) as standard interface
|
No REST access through ListData.svc to External Lists
|
Not applicable
|
Business Connectivity Services Client Runtime supports simultaneous installation of Office 2010 and Office 2013 on the same client computer.
For example, if Outlook 2010 and Lync 2013 are installed on the same client computer, this new feature enables Office 2010 and Office 2013 to continue to work without breaking.
|
Not applicable
|
Not applicable
|
No comments:
Post a Comment