Microsoft Office Tutorials and References
In Depth Information
■ you can’t configure an eCt data source with sss in sharepoint Foundation 2013. you have to use the user’s
identity or impersonated Windows identity only.
Did you realize that you haven’t seen or modified any XML file as you used to do in MOSS 2007? Do you now
agree how simple and easy it is to create an ECT in SharePoint 2013? But wait! What if the data source is not a database
but is actually a service that is delivering data, and this is the most common scenario your enterprise bus will have?
If you use the tools decision tree (refer back to Figure 4-9 ), you’ll see that for advanced solutions, you need to write a
custom .NET assembly connector.
Authoring an ECT Using Visual Studio with a .NET Connector
Before you begin actually creating the .NET assembly connector for the ECT using Visual Studio, let’s identify the
essential steps. Here’s what you’ll need to do:
Create stored procedures that enable the get item, get collection, and set item operations.
Author an external content type.
Develop a custom .NET Connector, and associate the above-mentioned operations
to the ECT.
author an eCt using visual studio, and generate actions—view and edit for individual items. Develop a .net
assembly connector to employee information in the employees table in the adventureWorks database. enable the
eCt to use the .net assembly connector, and, finally, create an external list using this eCt.
By the end of this exercise, you will have
a .net type assembly connector and
When you use the visual studio BDC template, you automatically obtain the BDC Model and external system along
with an eCt. But first, using Listings 4-1 through 4-3, create three stored procedures.
Listing 4-1. Stored Procedure for Retrieving All Employee Information
CREATE PROCEDURE [dbo].[uspGetEmployees]
SET NOCOUNT ON;
SELECT BusinessEntityID, NationalIDNumber, LoginID, JobTitle, BirthDate, MaritalStatus,
Search JabSto ::