This is the one more article of the BCS series. Learn how to create ECTs via Assembly .NET in SharePoint 2010 through Business Connectivity Services!

This approach will take advantage of the interface IContextProperty to get the BDC Connection details set against the BDC Model.

Enjoy it!

Creating ECTs via Assembly .NET

Creating ECTs via Assembly .NET just requires VS2010. The SPD2010 will not be used.

This approach can be applied in environments that:

Need to create business rules, which can be developed against the BDC model;

Use databases other than SQL Server, which can be implemented in the data access tier;

Require the deployment of WSP packages to activate features, which is automatically generated by VS2010;

If you have this scenario, this implementation has a higher level of difficulty by the level of details in creating the assembly .NET, which is displayed in the next sections of this article.

Working with Visual Studio 2010

The template called Business Data Connectivity Model will be used in this article. Start by opening up VS2010 and create a new project according to the Figure 1:

Figure 1 - Creating a new project and solution

Immediately after that a Wizard helps you in setting up the project. The URL needs to be validated for debugging purposes, and the solution will be created as a Farm Solution, according to the Figure 2:

Figure 2 – Wizard

Note: Once the project is created, delete the classes called Entity1 and Entity1Service. Don’t forget to delete the entity created which is available in the BDC Designer, because new classes will be generated in a new model.

Data Access Layer

Due to the fact the feature will be created as a package WSP, I preferred to provide data access in the same project. Some objects need to be added to manipulate the database, and for demonstration purposes I am using LINQ to SQL because it is simpler to implement. Add the LINQ to SQL object to the project and name it Dev.dbml, then create a new connection through the Server Explorer that uses Windows Authentication, open the database and drag the table Contact (Part II) according to the Figure 3:

Figure 3 - Adding table Contact

Before manipulating data of the Contact object, a class that contains CRUD methods needs to be created. So create a class called ContactManager and add the code below, whose comments are well documented:

Code Snippet

publicclassContactManager

{

///<summary>

/// Gets all the Contacts

///</summary>

///<returns>Contacts Array</returns>

publicContact[] GetContacts()

{

var contacts = newList<Contact>();

using (DevDataContext dev = newDevDataContext())

{

contacts = (from cont in dev.Contacts

select cont).ToList();

}

return contacts.ToArray();

}

///<summary>

/// Gets a specific Contact

///</summary>

///<param name="contactId">Contact Id</param>

///<returns>Returns the Contact</returns>

publicContact GetContactById(int contactId)

{

var contact = newContact();

using (DevDataContext dev = newDevDataContext())

{

contact = (from cont in dev.Contacts

where cont.ContactID == contactId

select cont).First();

}

return contact;

}

///<summary>

/// Updates a specific Contact

///</summary>

///<param name="contact">Contact to be updated</param>

publicvoid UpdateContact(Contact contact)

{

var contactDB = newContact();

using (DevDataContext dev = newDevDataContext())

{

contactDB = (from cont in dev.Contacts

where cont.ContactID == contact.ContactID

select cont).First();

// Alters the object

contactDB.Address = contact.Address;

contactDB.City = contact.City;

contactDB.CompanyName = contact.CompanyName;

contactDB.ContactName = contact.ContactName;

contactDB.ContactTitle = contact.ContactTitle;

contactDB.Country = contact.Country;

contactDB.Email = contact.Email;

contactDB.Fax = contact.Fax;

contactDB.Phone = contact.Phone;

contactDB.PostalCode = contact.PostalCode;

contactDB.Region = contact.Region;

// Submitting the changes

dev.Refresh(System.Data.Linq.RefreshMode.KeepChanges, contactDB);

dev.SubmitChanges();

}

}

///<summary>

/// Adds a Contact

///</summary>

///<param name="contact">New Contact</param>

publicvoid AddContact(Contact contact)

{

using (DevDataContext dev = newDevDataContext())

{

dev.Contacts.InsertOnSubmit(contact);

dev.SubmitChanges();

}

}

///<summary>

/// Deletes a Contacts

///</summary>

///<param name="contactId">Contact Id</param>

publicvoid DeleteContact(int contactId)

{

using (DevDataContext dev = newDevDataContext())

{

var contact = (from cont in dev.Contacts

where cont.ContactID == contactId

select cont).First();

dev.Contacts.DeleteOnSubmit(contact);

dev.SubmitChanges();

}

}

}

Note: This was already explained when creating ECTs via Web Services in part II, however as this is important in this demo, the same code was reused.

Create a new partial class called DevDataContext, as we already have this class automatically generated by Visual Studio. Create a new constructor, according to the code below:

Code Snippet

publicpartialclassDevDataContext

{

public DevDataContext() :

base(BdcModel1.ContactService.GetConnection(), mappingSource)

{

OnCreated();

}

}

Note: This new constructor contains a call to the method GetConnection(). It belongs to the ContactService class and returns the connection string, which is obtained directly from the BDC Metadata Model (we’ll check it soon).

BDC Model

By using the new BDC Panels in Visual Studio the Metadata Model will be created. It needs to be created based on the Data Access layer, as we will work with the Contact entity. Do this by using the BDC Designer Panel, according to the Figure 4:

Figure 4 - Contact entity added

As the Contact entity was created, now it must be configured. In order to do that add an Identifier called ContactID and the following Methods: GetConnection, ReadItem, ReadList, Delete, Update and Create. The context menu makes things easier, according to the Figure 5:

Figure 5 - Identifier and Methods added

To add and configure methods, the most convenient way is the utilisation of the BDC Method Details Panel (as this tool is going to generate XML automatically) according to the Figure 6:

Figure 6 - BDC Method Details Panel in action

The Table 1 below shows a summary of the configuration started in the Figure 6. It contains all the methods and signatures:

Option

Method

Parameters

Direction

Type Descriptor

Create Creator Method

Create

returnContact

Return

ReturnContact

newContact

In

NewContact

Create Deleter Method

Delete

contactID

In

ContactID

Create Finder Method

ReadList

contactList

Return

ContactList

Create Specific Finder Method

ReadItem

contact

Return

Contact

contactID

In

ContactID

Create Updater Method

Update

contact

In

Contact

Create Blank Method

GetConnection

parameter

Return

connection

Table 1 - Automatic method generation of the Contact entity

Note: A Blank Method will create a method called Method, which needs to be renamed. In this example call it GetConnection.

Before configuring the methods, make sure that the ContactID identifier type is System.Int32. Take the ReadItem method as the first one to be configured and click over the parameter (aka type descriptor) Contact, so we can select its type according to the Figure 7:

Figure 7 - TypeDescriptor type

The next step is to include new Type Descriptors to the Type Descriptor called Contact through BDC Explorer Panel, which basically represent its attributes. The Figure 9 displays how to add Type Descriptors and the Table 2 reveals the Type Descriptors to be added.

Figure 8 - Adding TypeDescriptors to Contact

Type Descriptor

Type

Address

System.String

City

System.String

CompanyName

System.String

ContactID

System.Int32

ContactName

System.String

ContactTitle

System.String

Country

System.String

Email

System.String

Fax

System.String

Phone

System.String

PostalCode

System.String

Region

System.String

Table 2 - Types of Type Descriptors

Once created, these Type Descriptors will be automatically reused when creating other methods. The code below shows the XML automatically generated of the Contact entity after configuring of all methods. This was extracted from the file called BdcModel1.bdcm:

Note: If you want to know more about the authentication types available through BCS, check the section References. Basically the XML above contains properties commonly used when creating connection strings.

BDC Model Entity Methods

Along the creation of methods through BDC Panels, Visual Studio took charge of the generation of the ContactService class and its respective methods. They are not implemented yet and are throwing an exception type of NotImplementedException.

Before coding all methods, do you remember the code that contains the method called GetConnection? It needs to return a database connection string, but how? Well, we are going to take advantage of the LobSystemInstance properties set previously.

But how to read the XML that contains those properties? Easy peasy! Just implement the interface IContextProperty in the ContactService class and the BDC does the trick for you.

Note: When an assembly contains a class that implements IContextProperty, its properties are automatically initialized at the time the assembly is executed in BDC. It helps a lot!

Do that by adding a reference to the assembly Microsoft.Business, which is available at the 14: \ISAPI\Microsoft.BusinessData.dll.

With the exception of the GetConnection method, all the others call CRUD methods from the ContactManager class. Still, in the Create and Update methods there is a validation of the required fields ContactName, Email and Phone, which cannot be null or empty as they throw an exception type of ObjectNotFoundException.

As expected the GetConnection method gets the properties of LobSystemInstance, which contains the BDC connection details, by returning the connection string used in the constructor of the DevDataContext Partial Class.

Creating the Deployment Package

Deployment of WSP packages in the real world is performed either manually or using scripts, not directly with the intervention of Visual Studio. I am explaining this for purposes of demonstration and understanding of STSADM.

Before generating the WSP package, some more settings are needed. Rename the feature to BdcModelFeature and add a property SiteUrl in the XML file BdcModelFeature.Template.xml that contains the URL for deployment, according to the Figure 9:

Figure 9 – Feature Property

Finally generate the WSP package by selecting Package in the context menu of Visual Studio. Get the WSP package from the Bin directory and by using STSADM deploy it with the following commands:

Configuring the External List

At this stage it is already possible to create an External List that will provide a visual interface to the external data in SharePoint 2010. Both SharePoint Designer and the SharePoint UI provides a way for us to create an External List, in the Part II I have showed how to use SharePoint Designer for this and now I am going to show how to create it by SharePoint UI.

Go to the web site and access Site Actions > More Options. The Figure 10 displays the modal dialog to select the External List:

Figure 10 – Selecting the External List

Then pick up the External Content Type ContactServices.BdcModel.BdcModel1.Contact and create the Contacts List, as displayed in the Figure 11:

Figure 11 - Creating the Contacts External List

After doing this you will get your Contacts List created. Is that all? No, you need to set permissions in the BDC Service Application for this Assembly, otherwise you will get the following screen:

Figure 12 – Access denied by Business Data Connectivity

Settings BDC Permissions

After the deployment of the .NET Assembly you need to set proper permissions in the BDC Service Application for users to see the external data. Go to the BDC Service Application in the Central Administration and find the .NET Assembly:

Figure 13 – Find the .NET Assembly

Then specify the users that are going to be allowed to see the external data, according to the Figure 14:

Figure 14 – Set Object Permissions

By doing this, refresh the External List (Figure 12) and you will get the external data.

This was advanced guys, from now on you are able to create your own ECTs via .NET Assemblies.

The BDC series is not yet finished, next time I will show how to interface ECTs with Client Applications. See you next time!

This is the fourth part of the article about the news in integrating external data with the Business Connectivity Services (BCS) in SharePoint 2010!

Just to recap, the Part I of this article brought an introduction to the BCS by the analysis of its architecture and components, the Part II brought the creation of External Content Types (ECT) via Database and the Part III the creation of ECTs via Web Service.

Part I reading is extremely important to understand this post. In this article I will explain the hierarchical structure of the Business Data Connectivity Metadata Model and introduce the new tools available in the Visual Studio 2010 to create BDC objects.

Have a good reading!

Understanding the BDC Metadata Model

In this article's example a new template in Visual Studio 2010 called Business Data Connectivity (BDC) Model will be used. It allows the creation of entities (BDC Entities) also known as External Content Types, an old friend of us (check Part I for more details).

Entities are objects that belong to the BDC metadata model and represent one of the core BDC metadata model objects. In this approach I want to go a little deeper into this model, check out the Figure 1:

Figure 1 - BDC Metadata Model

Now it is clear where the ECTs are within the BDC Metadata Model, but we still do not know in details the role performed by each one of the objects comprised in the Figure 1. We can only note that the objects are in a hierarchical structure.

To understand these objects let's check the details of each one:

NOTE: The same content can be found in the Reference links, however I have decided to drill down a little bit more than the content presented on MSDN. :)

Model - This is the BDC core main object that maps the external data. This is the aggregator of all the objects that comprise the hierarchy of this model.

LobSystem - Inside the model it behaves as the representation of an external service that contains the business logic, simply by defining the type of external data source to be used, that can be:

Database – Sets the mapping of a database;

DotNetAssembly – Defines the mapping of an assembly. NET;

Wcf – Defines the mapping of a WCF service endpoint;

WebService – Defines the mapping of a Web Service. It is considered "deprecated", so use a WCF service;

Custom – Defines the mapping of a custom connector, implemented to manage the external data source connection and data transferring.

LobSystemInstance - This is the implementation of a LobSystem. It holds all the connection details to an external service.

Entity - This is the representation within the BDC metadata model of an ECT, which according to the Part I describes the schema and data access capabilities of an external data source and its behaviour within Office and SharePoint.

Identifier - An identifier acts as a primary key in entities, the same concept used in tables.

Method - The methods are the behaviours of an entity. Within the metadata model it works as an aggregator of settings (FilterDescriptor, Parameter, MethodInstance) of the method that represents.

FilterDescriptor - Basically a FilterDescriptor can be created within a method to select both the input and the return of values. Several types of filters can be used (check the Reference links).

Parameter - Defines the parameter to be used inside the method, as follows:

In – Used to input parameters;

Out – Used to output parameters, similar to the parameter "out" in C#.

InOut – Represents a parameter that has two functions (input / output), similar to the parameter "ref" in C#.

Return – Sets a method return type. In the BDC this is considered as a return parameter.

TypeDescriptor - A TypeDescriptor is nothing more, nothing less than a definition to the parameter type. i.e.: Int32, String. It is recursive because it allows that other TypeDescriptor is referred as a parameter type.

MethodInstance - This is the implementation of a Method. Operations Create, Update, ReadItem, ReadList and Delete are already predefined for using.

Action - The actions allow the addition of extra functionalities to ECTs because they work as an additional link to external data. By default the actions View Item, Edit Item and Delete Item are added to the user interface (check the Reference links) and any further action added, such as a link to open a page, follows the ECT in any part of SharePoint.

ActionParameter - Sets the URL of the action that refers, so the link created works. It uses Identifiers or TypeDescriptors of the entity to create the URL.

AssociationGroup - Associations represent relationships between entities, similar to a relationship of tables. An AssociationGroup should be used to tie association methods, which are applied in a relationship of entities. i.e.: Given two entities Customer and Order, an AssociationGroup would store methods like GetOrderByCustomer and GetCustomerByOrder.

NOTE: In the next part of this lesson you will see the majority of these objects in use. This overview will be consolidated with a hands-on demo, especially when working with XML behind these definitions.

BDC Metadata Model Design Tool

Visual Studio 2010 was powered with several new design tools and the BDC was not forgotten. Now it's easy to create BDC models, because the toughest job (creation of objects) can be done visually and other small details manually in the XML generated.

The Figure 2 displays the new windows available in VS2010 to design BDC models:

Figure 2 - New windows to design BDC models

With the exception of the Properties window, three (3) new windows were added to the VS2010. They are:

BDC Designer - Enables the creation and edition of Entities, Identifiers, Methods and Associations between Entities. This is an design area that allows the creation of objects via drag-and-drop from the Toolbox window or even using the context menu (right mouse button).

BDC Method Details - As the name implies, it displays the configuration details of the methods. Allows creation and edition of methods, parameters, typedescriptors and filters (according to the BDC metadata model).

BDC Explorer - Organizes and displays BDC metadata model objects in a tree view. Its main purpose is to display objects in a hierarchical structure, but also allows the creation of TypeDescriptors and validation of objects.

Throughout the development in the next part you will see how to manipulate the BDC Metadata Model objects by using these panels. Stick around!

After a mini holiday here there is one more part of the BCS series, whose main approach is to show how to connect to different external data sources.

Learn how to integrate WCF services in SharePoint 2010 through Business Connectivity Services. This is a very interesting approach because it allows that different services (including the cloud) to be integrated into SharePoint 2010.

In this article a WCF service will be created, so an External Content Type (ECT) can be created.

Creating ECTs via Web Service (WCF)

In order to create ECTs via Web Service it is needed the utilisation of SPD2010 and in this case, due to the fact the Web Service is going to be coded from the scratch, VS2010 is required as well.

Use this type of approach in environments that:

Integrates with an external data source (i.e.: other systems), either on your Intranet or Internet;

There is a need for creating business rules (i.e.: any validation) which can be implemented during the creation of the Web Service;

Uses different databases rather than SQL Server, which can be implemented in a data access layer during the creation of the Web Service;

If you have this scenario, this implementation has a higher level of difficulty by creating the Web Service. Both VS2010 and SPD2010 are utilised, the former for the Web Service development and the latter for the configuration.

Working with Visual Studio 2010

The creation of the ECT in this approach is only possible with the existence of a Web Service, that's why a solution in VS2010 is going to be created. As already mentioned in the Block 1 of the BCS Architecture (Part I), both extensions .asmx (ASP.NET Web Service Application) and .svc (WCF Service Application) can be used in the creation of ECTs, and in this demonstration I am going to use a WCF Service Application.

Start VS2010, create a Blank Solution and add 3 projects according to the Figure 1:

Figure 1 - Creating the Solution

Note: Delete the files *.cs and App.config that are created by default in new projects.

The solution was split into projects that represent the data access and business logic layers. Some references between the projects need to be added, according to the Table 1:

Project

Reference

ContactServices.Business

ContactServices.Data

ContactServices.Host

ContactServices.Business

Table 1 - References

Note: In all code examples, my goal is just to show the functionality in creating an ECT in SharePoint 2010. Don’t forget to implement the best practices and patterns such as the Application Blocks (i.e.: Logging, Exception Handling, Security, etc...). I strongly recommend the use of Enterprise Library.

Data Access Layer

In order to create the project ContactServices.Data some objects that manipulate the database need to be added, and for demonstration purposes I use the LINQ to SQL because it is simpler to implement. Add this object to the project and name it Dev.dbml, then create a new connection that uses Windows Authentication using the Server Explorer, open the database and drag the table Contact (Part II) as displayed in Figure 2:

Figure 2 - Adding table Contact

Create a class that contains CRUD methods, so the object Contact can be handled. To do that, create a class called ContactManager and add the code below, which comments tell by themselves:

Code Snippet

publicclassContactManager

{

///<summary>

/// Gets all the Contacts

///</summary>

///<returns>Contacts Array</returns>

publicContact[] GetContacts()

{

var contacts = newList<Contact>();

using (DevDataContext dev = newDevDataContext())

{

contacts = (from cont in dev.Contacts

select cont).ToList();

}

return contacts.ToArray();

}

///<summary>

/// Gets a specific Contact

///</summary>

///<param name="contactId">Contact Id</param>

///<returns>Returns the Contact</returns>

publicContact GetContactById(int contactId)

{

var contact = newContact();

using (DevDataContext dev = newDevDataContext())

{

contact = (from cont in dev.Contacts

where cont.ContactID == contactId

select cont).First();

}

return contact;

}

///<summary>

/// Updates a specific Contact

///</summary>

///<param name="contact">Contact to be updated</param>

publicvoid UpdateContact(Contact contact)

{

var contactDB = newContact();

using (DevDataContext dev = newDevDataContext())

{

contactDB = (from cont in dev.Contacts

where cont.ContactID == contact.ContactID

select cont).First();

// Alters the object

contactDB.Address = contact.Address;

contactDB.City = contact.City;

contactDB.CompanyName = contact.CompanyName;

contactDB.ContactName = contact.ContactName;

contactDB.ContactTitle = contact.ContactTitle;

contactDB.Country = contact.Country;

contactDB.Email = contact.Email;

contactDB.Fax = contact.Fax;

contactDB.Phone = contact.Phone;

contactDB.PostalCode = contact.PostalCode;

contactDB.Region = contact.Region;

dev.Refresh(System.Data.Linq.RefreshMode.KeepChanges, contactDB);

dev.SubmitChanges();

}

}

///<summary>

/// Adds a Contact

///</summary>

///<param name="contact">New Contact</param>

publicvoid AddContact(Contact contact)

{

using (DevDataContext dev = newDevDataContext())

{

dev.Contacts.InsertOnSubmit(contact);

dev.SubmitChanges();

}

}

///<summary>

/// Deletes a Contacts

///</summary>

///<param name="contactId">Contact Id</param>

publicvoid DeleteContact(int contactId)

{

using (DevDataContext dev = newDevDataContext())

{

var contact = (from cont in dev.Contacts

where cont.ContactID == contactId

select cont).First();

dev.Contacts.DeleteOnSubmit(contact);

dev.SubmitChanges();

}

}

}

Business Logic Layer

The project ContactServices.Business should contain Interfaces and Classes that call methods of the ContactServices.Data project. Creating Interfaces are important because of 3 main reasons in this Solution:

To perform that, create the interface IContactServices and the class called ContactServices that implements it, according to the code below:

Code Snippet

[ServiceContract]

publicinterfaceIContactServices

{

[OperationContract]

Contact[] GetContacts();

[OperationContract]

Contact GetContactById(int contactId);

[OperationContract]

void UpdateContact(Contact contact);

[OperationContract]

void AddContact(Contact contact);

[OperationContract]

void DeleteContact(int contactId);

}

Code Snippet

publicclassContactServices : IContactServices

{

#region IContactServices Members

publicContact[] GetContacts()

{

// Create your own business rules

returnnewContactManager().GetContacts();

}

publicContact GetContactById(int contactId)

{

// Create your own business rules

returnnewContactManager().GetContactById(contactId);

}

publicvoid UpdateContact(Contact contact)

{

// Create your own business rules

newContactManager().UpdateContact(contact);

}

publicvoid AddContact(Contact contact)

{

// Create your own business rules

newContactManager().AddContact(contact);

}

publicvoid DeleteContact(int contactId)

{

// Create your own business rules

newContactManager().DeleteContact(contactId);

}

#endregion

}

The class ContactServices contains CRUD methods that are going to be used by the BCS and tell by themselves. They work as a "thin layer" for handling data, because directly call the ContactManager methods in the project ContactServices.Data.

In this example no business rules were implemented, but you can if you need them. Just code against the methods above.

Service Host

The project ContactServices.Host was created to work as the WCF Service host, which let methods to be available for BCS consuming. Start renaming the file Service1.svc to ContactServices.svc and update the service reference at the page directive:

This change is necessary because the ContactServices class needs to be mapped, which was implemented in the project ContactServices.Business. An update in the Web.config is also necessary, by editing it in the WCF Service Configuration Editor (available in the VS2010) or directly in the section system.serviceModel according to the code below:

Note: The behavior serviceDebug contains the attribute includeExceptionDetailInFaults to list in details any Web Service problem in the SharePoint Log, which is very useful during the WCF integration tests.

In the end, your solution should be similar to the Figure 3:

Figure 3 – Final Solution

Deploy the solution in the IIS, so you can get the Url for creating the ECT, as demonstrated in the next sections.

Working with SharePoint Designer 2010

At this stage the solution was already created, and now the ECT needs to be created, by mapping the Web Service methods and parameters. The Figure 1 (Part II) displays the first step in creating the ECT, afterwards add a new connection (1) to the Web Service by choosing the External Data Source Type (2), according to the Figure 4:

Figure 4 - Creating a new connection

Set the connection parameters according to the Figure 5:

Figure 5 – WCF Connection details

Note: Some important considerations:

The WCF metadata can be obtained through WSDL or endpoint Mex. Both of them can be informed in the fields Service Metadata URL / Metadata Connection Mode, and are available in this solution.

The User’s Identity can be used to connect to the WCF service and hence to the database, that’s why the Windows Authentication is required.

After creating the WCF connection the CRUD operations need to be mapped. This is the stage in which the Web Service methods and parameters should be mapped for the creation of the ECT. For each figure below there is an operation whose parameters are displayed in tables:

Figure 6 - AddContact Operation Properties

The operation AddContact as shown in Figure 6 has the following Input parameters according to the Tables 2 and 3:

Element

.NET Type

Map to Identifier

Identifier

Field

Display Name

Foreign Identifier

ContactID

System.Int32

TRUE

ContactID

ContactID

ID

Address

System.String

FALSE

Address

Address

City

System.String

FALSE

City

City

CompanyName

System.String

FALSE

CompanyName

Company Name

ContactName

System.String

FALSE

ContactName

Contact Name

ContactTitle

System.String

FALSE

ContactTitle

Contact Title

Country

System.String

FALSE

Country

Country

Email

System.String

FALSE

Email

E-mail

Fax

System.String

FALSE

Fax

Fax

Phone

System.String

FALSE

Phone

Phone

PostalCode

System.String

FALSE

PostalCode

Postal Code

Region

System.String

FALSE

Region

Region

Table 2 - AddContact Operation Input Parameters

Element

Default Value

Filter

Element Path

ContactID

<<None>>

contact.ContactID

Address

<<None>>

contact.Address

City

<<None>>

contact.City

CompanyName

<<None>>

contact.CompanyName

ContactName

<<None>>

contact.ContactName

ContactTitle

<<None>>

contact.ContactTitle

Country

<<None>>

contact.Country

Email

<<None>>

contact.Email

Fax

<<None>>

contact.Fax

Phone

<<None>>

contact.Phone

PostalCode

<<None>>

contact.PostalCode

Region

<<None>>

contact.Region

Table 3 - AddContact Operation Input Parameters (Continuation)

There are no Return parameters to be configured for the operation AddContact, so simply ignore the configuration screen and finish this mapping.

Figure 7 - DeleteContact Operation Properties

The operation DeleteContact as shown in Figure 7 has the following Input parameter according to the Table 4:

Element

.NET Type

Map to Identifier

Identifier

Display Name

Default Value

Filter

Element Path

contactId

System.Int32

TRUE

ContactID

ID

<<None>>

contactId

Table 4 - DeleteContact Operation Input Parameters

Figure 8 - GetContactById Operation Properties

The operation GetContactById as shown in Figure 8 has the following Input and Return parameters according to the Tables 5, 6 and 7:

Element

.NET Type

Map to Identifier

Identifier

Display Name

Default Value

Filter

Element Path

contactId

System.Int32

TRUE

ContactID

ID

<<None>>

contactId

Table 5 - GetContactById Operation Input Parameters

Data Source Element

.NET Type

Map to Identifier

Identifier

Field

Display Name

Foreign Identifier

ContactID

System.Int32

TRUE

ContactID

ContactID

ID

Address

System.String

FALSE

Address

Address

City

System.String

FALSE

City

City

CompanyName

System.String

FALSE

CompanyName

Company Name

ContactName

System.String

FALSE

ContactName

Contact Name

ContactTitle

System.String

FALSE

ContactTitle

Contact Title

Country

System.String

FALSE

Country

Country

Email

System.String

FALSE

Email

E-mail

Fax

System.String

FALSE

Fax

Fax

Phone

System.String

FALSE

Phone

Phone

PostalCode

System.String

FALSE

PostalCode

Postal Code

Region

System.String

FALSE

Region

Region

Table 6 - GetContactById Operation Return Parameters

Data Source Element

Element Path

Required

Read-Only

Office Property

ContactID

GetContactById.ContactID

FALSE

TRUE

Custom Property

Address

GetContactById.Address

FALSE

FALSE

Business Address (BusinessAddress)

City

GetContactById.City

FALSE

FALSE

Business Address City (BusinessAddressCity)

CompanyName

GetContactById.CompanyName

FALSE

FALSE

Company Name (CompanyName)

ContactName

GetContactById.ContactName

TRUE

FALSE

Full Name (FullName)

ContactTitle

GetContactById.ContactTitle

FALSE

FALSE

Title (Title)

Country

GetContactById.Country

FALSE

FALSE

Business Address Country/Region (BusinessAddressCountry)

Email

GetContactById.Email

TRUE

FALSE

Email 1 Address (Email1Address)

Fax

GetContactById.Fax

FALSE

FALSE

Business Fax Number (BusinessFaxNumber)

Phone

GetContactById.Phone

TRUE

FALSE

Business Telephone Number (BusinessTelephoneNumber)

PostalCode

GetContactById.PostalCode

FALSE

FALSE

Business Address Postal Code (BusinessAddressPostalCode)

Region

GetContactById.Region

FALSE

FALSE

Business Address State (BusinessAddressState)

Table 7 - GetContactById Operation Return Parameters (Continuation)

Figure 9 - GetContacts Operation Properties

The operation GetContacts as shown in Figure 9 does not have Input parameters to be configured, but has the following Return parameters according to the Tables 8 and 9:

Element

.NET Type

Map to Identifier

Identifier

Field

Display Name

Foreign Identifier

ContactID

System.Int32

TRUE

ContactID

ContactID

ID

Address

System.String

FALSE

Address

Address

City

System.String

FALSE

City

City

CompanyName

System.String

FALSE

CompanyName

Company Name

ContactName

System.String

FALSE

ContactName

Contact Name

ContactTitle

System.String

FALSE

ContactTitle

Contact Title

Country

System.String

FALSE

Country

Country

Email

System.String

FALSE

Email

E-mail

Fax

System.String

FALSE

Fax

Fax

Phone

System.String

FALSE

Phone

Phone

PostalCode

System.String

FALSE

PostalCode

Postal Code

Region

System.String

FALSE

Region

Region

Table 8 - GetContacts Operation Return Parameters

Element

Element Path

Required

Read-Only

Show in Picker

Timestamp Field

ContactID

GetContacts.GetContactsElement.ContactID

FALSE

TRUE

FALSE

FALSE

Address

GetContacts.GetContactsElement.Address

FALSE

FALSE

FALSE

FALSE

City

GetContacts.GetContactsElement.City

FALSE

FALSE

FALSE

FALSE

CompanyName

GetContacts.GetContactsElement.CompanyName

FALSE

FALSE

FALSE

FALSE

ContactName

GetContacts.GetContactsElement.ContactName

TRUE

FALSE

FALSE

FALSE

ContactTitle

GetContacts.GetContactsElement.ContactTitle

FALSE

FALSE

FALSE

FALSE

Country

GetContacts.GetContactsElement.Country

FALSE

FALSE

FALSE

FALSE

Email

GetContacts.GetContactsElement.Email

TRUE

FALSE

FALSE

FALSE

Fax

GetContacts.GetContactsElement.Fax

FALSE

FALSE

FALSE

FALSE

Phone

GetContacts.GetContactsElement.Phone

TRUE

FALSE

FALSE

FALSE

PostalCode

GetContacts.GetContactsElement.PostalCode

FALSE

FALSE

FALSE

FALSE

Region

GetContacts.GetContactsElement.Region

FALSE

FALSE

FALSE

FALSE

Table 9 - GetContacts Operation Return Parameters (Continuation)

Figure 10 - UpdateContact Operation Properties

The operation UpdateContact as shown in Figure 10 has the following Input parameters according to the Tables 10 and 11:

Element

.NET Type

Map to Identifier

Identifier

Field

Display Name

Foreign Identifier

ContactID

System.Int32

TRUE

ContactID

ContactID

ID

Address

System.String

FALSE

Address

Address

City

System.String

FALSE

City

City

CompanyName

System.String

FALSE

CompanyName

Company Name

ContactName

System.String

FALSE

ContactName

Contact Name

ContactTitle

System.String

FALSE

ContactTitle

Contact Title

Country

System.String

FALSE

Country

Country

Email

System.String

FALSE

Email

E-mail

Fax

System.String

FALSE

Fax

Fax

Phone

System.String

FALSE

Phone

Phone

PostalCode

System.String

FALSE

PostalCode

Postal Code

Region

System.String

FALSE

Region

Region

Table 10 - UpdateContact Operation Input Parameters

Element

Default Value

Filter

Element Path

ContactID

<<None>>

contact.ContactID

Address

<<None>>

contact.Address

City

<<None>>

contact.City

CompanyName

<<None>>

contact.CompanyName

ContactName

<<None>>

contact.ContactName

ContactTitle

<<None>>

contact.ContactTitle

Country

<<None>>

contact.Country

Email

<<None>>

contact.Email

Fax

<<None>>

contact.Fax

Phone

<<None>>

contact.Phone

PostalCode

<<None>>

contact.PostalCode

Region

<<None>>

contact.Region

Table 11 - UpdateContact Operation Input Parameters (Continuation)

Note: Notice that in most cases just the configuration parameters (columns) nomenclature changes, but data is the same. I have decided to create configuration tables for each operation in order to facilitate the mapping with separate operations.

Once all the columns were set properly, save the ECT (1) and check the operations created (2), which can be edited at any time, according to the Figure 11:

Figure 11 - Saving the ECT

Now it is possible to create an External List that will provide a visual interface for the external data in SharePoint 2010. In the same screen of External Content Types, choose the option External List on the context menu. Name it to “Contacts”, according to the Figure 12:

Figure 12 - Creating an External List

When the External List is created, the purpose of this article is accomplished. Now it is up to you to test the External List, which was already explained in the Part II. Reuse the same test and apply it here, since it was created for this purpose.

The fact of using a Web Service for integration in SharePoint 2010 shows us that it is possible to transmit data from and to any system that provides this interface. Unify data from different systems in SharePoint 2010! Now you know how to do it!