Going thru BCS in one of the application but found following limitations with.
Any body out there who could suggest me with something or say any use of third party tool
BCS External List Limitations
1) Workflows cannot be configured on External Lists
2) Cannot create Information Management Policies
3) No versioning or version history
4) No Inline Editing or Datasheet View
5) No ratings
6) No ability to Export to Excel, Create Visio Diagram, Open with Access or Open with Project
7) No REST access through ListData.svc to External Lists
8 ) No RSS Feeds
9) No Item Level Permissions
10) No item or field level validation
11) No Lookups
12) No attachments
Todas as Respostas
BCS is not the only one method of accessing data from external sources.
You can use methods without these limitations such as:
-completely custom webparts developing
-standard storing data inside sharepoint(not in external source).
The best choice depends on your goals. Every method have different cost, time and business value for customer.
Ivan Gorbadey. Sharepoint 2010 MCPD & MCITP.
You could create an Enttity Framework Model in one project. Then in a second project in the same solutin, create a wcf data services that exposes the EF Model as rest. That can be deployed to SharePoint. In a third project in the solution you can create a BCS .net assembly connector that uses the EF Model.
This will expose an EF Model using both rest and External Content Types in sharepoint.
You wrote: standard storing data inside sharepoint
I am impressed that you would even write that down. Yes, I guess we could trash all of our external systems and store EVERYTHING inside of SHAREPOINT, I just was not smart enough to realize that.
Let's keep it positive, Ivan didn't mean to imply that you should take down all your external systems and migrate the contents to SharePoint. On a related note, the following Wiki page discusses benefits of storing data in a database, list or external list: http://social.technet.microsoft.com/wiki/contents/articles/9638.sharepoint-2010-best-practice-keep-relational-data-in-a-database-or-migrate-it-into-a-custom-list.aspx To be clear, those options don't prevent the use and usefulness of other legacy systems or storage types.