Skip to main content

SharePoint 2013 - Setting Up External Content Type

There were earlier posts where we discussed External Content Types setup for SharePoint 2010:

Setting up External Content Type for SQL Server database using SQL Server authentication - SharePoint 2010 Foundation

External Content Types - Reload - Setting up for SQL Server database using SQL Server authentication - SharePoint 2010 Server

This one is about creating connection to the custom SQL Server database (External System) in SharePoint 2013.

1. Create Secure Store Service Target Application

1.1. Go to Central Administration -> Manage Service Applications -> Secure Store Service Application. Click "Generate New Key" if required:


1.2. Provide Pass Phrase:


1.3. Create "New" to create new Target Application:


1.4. Provide the name and other parameters and click "Next":


Note: It's good idea to specify "Group" for Target Application Type. In that case you would be able to manage access to the external data using Active Directory groups rather that individual user accounts.

1.5. Provide fields that are going to be used in this Secure Store Target Application. In my case it is just Windows User Name and Password fields:


1.6. Specify Administrators:


1.7. Set credentials for the newly created Secure Store Target Application:



Now we are ready to create new External Content Type to work with custom external data.

2. Creating External Content Type using SharePoint Designer 2013

2.1. Open SharePoint Designer -> Open Site -> External Content Types -> New External Content Type:



2.2. Provide the name and click External System link to specify external data parameters:


2.3. Click "Add Connection" button:


2.4. The choices are "SQL Server", "WCF Service" and "NET. Type":



We are selecting "SQL Server" in our case.

2.5. Specify data connection properties. Select "Connect with Impersonated Custom Identity" and provide the name of Secure Store Target Application name that was created earlier:


2.6. Specify the table, view or stored procedure that will be used in External Content Type and generate the necessary actions:

2.6.1.

2.6.2.


2.6.3. Select the field which will be used as identifier:


2.6.4. Specify filters if required:


2.6.5. Done:

2.7. Set the Title:


2.8. Set up permissions to manage and execute External Content Type. Go to Central Administration -> Manage Service Applications -> Business Connectivity Service Application:


2.9. Select the newly created External Content Type and click "Set Object Permissions" button for individual object or click "Set Metadata Store Permissions" to apply permissions to all objects:


Note: In order to use External Content Type in SharePoint as end user the "Execute" and "Selectable In Clients" permissions level is enough.

Now we are ready to use the new External Content Type on our SharePoint site.

3. Create an External List if necessary.

3.1. Select External Content Type in SharePoint Designer and click "Create Lists & Form" button:


3.2. Specify the list name and select an option to create InfoPath Form if necessary:


Done.

Stay tuned for more fun with SharePoint 2013.

Comments

  1. Thank you for the information. You have a very good article. I found it informative and useful. Keep up the good work and God bless!

    Caren
    www.gofastek.com

    ReplyDelete
  2. I like what you guys are up too. Such intelligent work and reporting!Keep up the excellent works guys I have incorporated
    sharepoint online training

    ReplyDelete
  3. Good article on SharePoint External Content Types setup, exclude the usefulness images in between then content looks more interesting to the audience.

    Best Regards,
    SharePoint 2013 Online Training in Hyderabad

    ReplyDelete

Post a Comment

Popular posts from this blog

Setting up External Content Type for SQL Server database using SQL Server authentication - SharePoint 2010 Foundation

This post is a follow up on the issues that I have got setting up External Content Type (ECT) on SharePoint 2010 Foundation that was going to connect to remote SQL Server database for information. I cannot use my SharePoint user accounts to access SQL Server. According to the information I have discovered ECT and Business Connectivity Services are available in the SharePoint 2010 Foundation, but there are some issues if you want to use authentication methods in your external connections that are different from Windows Identity or Current User Identity. This is because there is no Secure Store Service in SharePoint 2010 Foundation which serves as an impersonation hub and is only available in SharePoint 2010 Server edition. The issues are coming from the fact that you can actually create ECT in SharePoint Designer 2010 providing just Secure Store ID and system would ask you for credentials and here you go, but when you try to use your ECT in External Lists or as a lookup columns you w...

SharePoint 2013 Development and Consulting - Laptop & Conferencing Experience with Lync

Have just jumped on a brand new SharePoint 2013 massive Intranet project and because of specific working conditions have found some items that required addressing almost immediately in order to continue the job. Maybe this will be interesting to someone else who is about to start SharePoint 2013 development to have an idea of what might be necessary. I started working with SharePoint using my own infrastructure in 2009. I used iMac with 320GB HDD and 4GB RAM running VMWare Fusion to virtualise Windows  environment ( SQL Server 2008, standalone SharePoint 2007, Visual Studio 2008, Office 2007). It was all-in-one virtual machine. A bit slow, but enough for any SharePoint work that I had at that time. For communication with colleagues and partners we used GoToMeeting . Great tool that worked (and still works) without any problems. Voice, video, screen-sharing - all worked well using built-in audio/video hardware. In 2010 I got a MacBook Pro  with 500GB HDD and 8GB ...

InfoPath 2013 Preview - URL not valid error when publishing

In InfoPath 2010 there is a problem when you try to publish a Form to a SharePoint site that doesn't have root site collection. You will get an error message "The following url is not valid". It's described here:   http://support.microsoft.com/kb/981854 The solution is to create root site collection for the Web application. Same problem is with InfoPath 2013: In my situation I didn't create the root site collection initially, but used "/sites" managed path instead for all site collections. To solve the problem with InfoPath I had to create it. Used a new site template "Project Site". Will get a chance to research that too. :)