Skip to main content

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

In the previous post I wrote how to properly set up an External Content Type for SQL Server in SharePoint 2010 Foundation.

Reality is that even in Server edition we have Secure Store Service which was an issue in Foundation edition - we need to do some tricks before we can use created ECT in SharePoint 2010 Server.

Alright girls and boys, let's move on.

1. After you have created an ECT in SharePoint Designer check the name of Secure Store Application:


2. Go to Secure Store Service settings in Central Administration:

3. Select New command from the ribbon to create new Secure Store Target Application:


4. Type the name - in my case it is SecureStoreWyldeCRM - and other related parameters and click Next:


5. Add two credential fields - User name and Password. One of type User Name and another of type Password and hit Next:


6. Set administrators for the application and click Next:


7. Now when you see newly created Target Application hit Set command on the ribbon to set credentials for this application so it could connect to the database:

8. Specify database user name and password and hit OK:


9. Enjoy working with the ECT that can connect to your SQL Server database through SharePoint!


If you have any questions in regard to External Content Types, you need assistance or if you think you don't know how you could benefit from using External Content Types for your business - contact us now for a consultation.

Stay tuned for more articles from Wylde Solutions.
Labels:

Comments

  1. UnknownNovember 10, 2014 at 9:44 PM

    Thank you for putting an effort to published this article. You've done a great job! Good bless!

    Caren
    www.gofastek.com

    ReplyDelete
  2. UnknownNovember 6, 2016 at 4:18 PM

    If you are not willing to learn, No one can help you. If you are determined to learn, No one can stop you.
    imarksweb.net

    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...
37 comments
Read more

Document Sets - SharePoint 2010 - Part 1

Hi again, in this post I am going to demonstrate how set up and start using Document Sets in SharePoint 2010. In Beta version there was a little problem when working with Document Sets. You could see the discussion around it here: Document Set content type issue . Now it is fixed and I will show you how to set up Document Sets properly to also use Keywords. 1. Activate two site collection features - Document Sets and Document ID Service: 2. Select a document library settings where you want to implement Document Sets. In my case it is Shared Documents. When you have selected the settings go to Advanced settings and then allow content types management: 3. Add an existing content type called Document Set: 4. Now I want to create a new Document Set. I have a sales opportunity and I have two documents related to this sales opportunity. So first I select New Document -> Document Set command, then provide name and description and there it is: 5. To check if our Document ID...
15 comments
Read more

Version control in Office 365

When working with documents in SharePoint or Office 365, quite often files are named like "Project-Budget-Report-v1.55", "Project-Budget-Report-v1.56", "Project-Budget-Report-v2.0" etc. and stored in the same folder or library. This is to achieve version control from the user perspective. This is not a good idea for the following reasons: Storing redundant information Confusion which version to use when Browsing though many documents to see what information/metadata changed if required Version numbering should be automated, no time spent by the document author There is a better way to manage versions of documents and to use tools already available to us in Office 365. File name should not contain the version number in it. Every time you upload a document with the same name the SharePoint will increment the version number for you automatically in the current set up of our Office 365 site we use for customer documentation. Then to manage the...
Post a Comment
Read more