- Approval of items is not supported.
- Attachments are not supported directly.
- Check-in and checkout of items are not supported.
- Using standard site content types in External Lists is not supported.
- Drafts of items are not supported.
- Send-To operations are not supported.
- List event handlers are not supported.
- Datasheet View is not supported.
- Querying through LINQ to SharePoint is not supported.
- Document templates are not supported.
- Versioning of items is not supported.
- Starting workflows from items is not supported, but workflows can read or write to External Lists through the SPList object.
- Validation formulas are not supported.
Can’t connect data to workflows
There is no way for you to run a workflow on records contained in external lists. In SharePoint 2010 you can only attach workflows to documents, list items and content types – not external lists. You could map external list records to SharePoint lists and connect a workflow to the internal list, but think about what’s needed to sync the two lists.
Lack of record-level permissions
This means you can’t control who has access to specific records in the external list – like marketing staff being able to view but not change entries belonging to sales.
No REST access
You cannot get external data that sits somewhere out on the web, like SaleForce.com.
No attachment support
SharePoint BCS 2010 does not allow for attachments, so you can’t link a record to a relevant document. Well, you might be able to store the attachment in the external database, but read on…
No BLOB write support
You can’t write to a BLOB field through BCS, unless you come up with your own write method.
Can’t export data to Excel
…or other popular file formats, but if the data has numbers in it users are going to be asking you how to get it into Excel (“cut and paste” wasn’t well received when I tried suggesting it).
No datasheet view and inline editing
This means you cannot edit items directly when viewing them as a grid. You need to open the individual item view to edit the contents.
Lack of field and record level validation
You can’t control what a user enters into the field without resorting to the intricacies of SharePoint Designer or InfoPath.
Limited lookup functionality
When you retrieve a value of “2732” in the Industry Code field of your CRM contact, that’s all you’re going to see since you can’t link the field to the Industry Codes table. The ID column is the one thing that you can look up on external lists; otherwise you’ll have to start coding to be able to get “Book Printing” instead of a cryptic number.
Lack of alerts
You can’t configure alerts on external lists through BCS.
Lack of RSS feeds
When using BCS in SharePoint 2010, RSS feeds are not accessible.
Lack of ratings
One can’t rate items that are contained in an external list.
No versioning
You can’t keep a version history of changes to external lists, but maybe you couldn’t in the original system ether…
While SharePoint BCS 2010 (Business Connectivity Services) lets you connect to and access external, it does present several challenges when you have to build a business application in SharePoint. Some are big limitations, while others are just annoyances:
Can’t connect data to workflows
There is no way for you to run a workflow on records contained in external lists. In SharePoint 2010 you can only attach workflows to documents, list items and content types – not external lists. You could map external list records to SharePoint lists and connect a workflow to the internal list, but think about what’s needed to sync the two lists.
Lack of record-level permissions
This means you can’t control who has access to specific records in the external list – like marketing staff being able to view but not change entries belonging to sales.
No REST access
You cannot get external data that sits somewhere out on the web, like SaleForce.com.
No attachment support
SharePoint BCS 2010 does not allow for attachments, so you can’t link a record to a relevant document. Well, you might be able to store the attachment in the external database, but read on…
No BLOB write support
You can’t write to a BLOB field through BCS, unless you come up with your own write method.
Can’t export data to Excel
…or other popular file formats, but if the data has numbers in it users are going to be asking you how to get it into Excel (“cut and paste” wasn’t well received when I tried suggesting it).
No datasheet view and inline editing
This means you cannot edit items directly when viewing them as a grid. You need to open the individual item view to edit the contents.
Lack of field and record level validation
You can’t control what a user enters into the field without resorting to the intricacies of SharePoint Designer or InfoPath.
Limited lookup functionality
When you retrieve a value of “2732” in the Industry Code field of your CRM contact, that’s all you’re going to see since you can’t link the field to the Industry Codes table. The ID column is the one thing that you can look up on external lists; otherwise you’ll have to start coding to be able to get “Book Printing” instead of a cryptic number.
Lack of alerts
You can’t configure alerts on external lists through BCS.
Lack of RSS feeds
When using BCS in SharePoint 2010, RSS feeds are not accessible.
Lack of ratings
One can’t rate items that are contained in an external list.
No versioning
You can’t keep a version history of changes to external lists, but maybe you couldn’t in the original system ether…
No comments:
Post a Comment