Skip to main content

Business Data Connectivity

I came to a requirement wherein I was supposed to get data from an 3rd party portal using API’s and then bring them to SharePoint server.

The first approach that I finalized was just to make BDC solution that will get data from 3rd party portal and will deploy it to SharePoint.

How to Create BDC solution in SharePoint?

I found below link that is having really great description about hot to create and deploy the BDC solution to SharePoint.

http://www.c-sharpcorner.com/uploadfile/hung123/creating-business-data-connectivity-service-using-visual-studio-2010/

After creating an POC I came to know that BDC model cannot be deployed on Multi tenant farm.

So what can be done next? After some amount of googling I came to know that we can create BDC solution using WCF services also.

So I created a WCF service solution that acted as a wrapper that used to fetch data from the portal.

We can them publish that service to IIS or Server and use the service reference in to SharePoint designer in order to create and External List. Below is the link that helped me for doing this.

https://msdn.microsoft.com/en-us/library/office/ff953200(v=office.14).aspx

Conclusion:
             1.       You cannot deploy BDC model that is created in Visual studio to Multi-tenant farm.
             2.       WCF services can be used as BDC solution in SharePoint environment independent of                         whether it is Multi-tenant or not.

Regards,
Keyur Pandya

Comments

  1. RobustPost16 March 2021 at 12:08

    Wow! This could be one of the most useful blogs we have ever come across on thesubject. Actually excellent info! I’m also an expert in this topic so I can understand your effort. Get More Info

    ReplyDelete
    Replies
    1. Keyur Pandya2 April 2021 at 11:19

      Thanks for your comment, Good the see this helps.

      Delete

Post a Comment

Popular posts from this blog

Identity client runtime library (IDCRL) did not get a response from the login server.

Recently I was doing some testing with a background PowerShell and encountered a weird error. “Identity client runtime library (IDCRL) did not get a response from the login server”. The error that you might encounter while working with PowerShell. This error is very misleading when it comes to identifying what could go wrong. After doing quite a good amount of research below are the probable causes for the error. Invalid Credentials MFA (Multi-Factor Authentication) Manage security defaults. Solutions Invalid Credentials Check if your credentials are wrong. Especially if you are using variables. MFA (Multi-Factor Authentication) Check if MFA is enabled on the account which you are using. These only affect you badly if you are developing PowerShell for a background Job. Go to Microsoft 365 admin center Users -> Active users -> Select the user -> Manage multifactor authentication -> Select the user -> Disable multi-factor authentication. M
2 comments
Read more

New-PnPTenantSite: The remote server returned an error: (401) Unauthorized.

New-PnPTenantSite: The remote server returned an error: (401) Unauthorized. Recently I was working on automate SharePoint site provisioning PnP script. We wanted to schedule this script to auto trigger on hourly basis, so we scheduled the script. As the script was to be scheduled one, we started creating SharePoint Apps to manage authentication. Register SharePoint Add-ins Go to <site collection url>/_layouts/15/AppRegNew.aspx by using a web browser. AppRegNew page form Enter values for the follow form fields: Add-in ID . Also known as client ID; a GUID that can be generated (when you select Generate ) or pasted into AppRegNew.aspx. The value must be unique for each add-in and must be lowercase .   Add-in Secret . Also known as the client secret, an opaque string. It is generated on the AppRegNew.aspx page by using the Generate button. Title:  A user-friendly title: for example, Contoso photo print
Post a Comment
Read more