{"loaderData":{"0-13":{"posts":[{"id":57,"slug":"how-to-create-a-searchable-sharepoint-2010-bdc-net-assembly-connector-which-reads-from-a-flat-file","title":"HOW TO: Create a Searchable SharePoint 2010 BDC .NET Assembly Connector Which Reads From A Flat File","content":"\n

The Business Context

In many large organizations business data is stored inside of flat files from mainframes or other legacy systems. These systems chug along just fine everyday and support many key elements of the business; they aren’t going away anytime soon. Traditionally, accessing flat file data, making it viewable in a web pages, and making it searchable requires an enormous amount of custom code.

The Solution

New functionality inside SharePoint 2010’s Business Connectivity Services (BCS) makes it extremely easy to connect to flat file data sources (or any other data source), display it in web pages, and make it searchable. This blog post is the first in a 2 part series which describes how to create a SharePoint 2010 BCS .NET Assembly Connector to read data from a flat file and register it as an external content type in SharePoint. Part 2 of this blog post series (coming tomorrow) demonstrates how to register an external content type with the SharePoint search service to make the data searchable.

As you may already know, SharePoint 2010’s BCS provides the ability to connect databases, web services, and WCF services right out of the box. In the last version of SharePoint if we wanted to connect to another type of data source we would create a web service to connect to the data source then connect the BDC to our custom web service. That’s no longer how things are done. Now, a .NET Assembly Connector is used to connect to data sources the BCS does not natively support. A .NET Assembly Connector is a .NET assembly which the BCS uses as a proxy to connect to data sources. The .NET Assembly Connector defines the entities returned from the data source and includes the implementation code to connect to the data source and return the information.

This example shows how a .NET Assembly Connector may be used for read operations, however they may also be used for write operations. I will be posting another blog post on that topic shortly.

Nick Swan is also actively working with the SharePoint 2010 BCS. You can read more posts about this topic his blog:

BCS Shims – .NET assembly as a data source for Business Connectivity Services
\nBusiness Data Connectivity Model – Finder Method

Create the flat file data source

This example reads data from a flat file located on the SharePoint server. It is unlikely that you will be reading the contents of a flat file located on your SharePoint server, most likely the file will be stored on a file share on your network. To keep the example simple I’m placing the flat file on the SharePoint server.

To create the flat file (data source) follow these steps:

Create the following directory on your SharePoint server\n
```
C:DATA
```
\n
Open your favorite text editor and create a file called flat-file-data-source.txt

Paste the following sample data into the file\n

1,Contoso,Orlando,Gee,8713 Yosemite Ct.,Bothel,WA,98011,555-123-4567,1:23 PM 11/3/2009
2,AdventureWorks,Keith,Harris,1318 Lasalle Street,Bothel,WA,98011,555-246-8102,3:23 PM 11/3/2009
3,Litware,Donna,Carreras,9178 Jumping St.,Dallas,TX,75201,555-987-6543,5:23 PM 11/3/2009
4,Progressive Sports,Janet,Gates,9228 Via Del Sol,Phoenix,AZ,85004,555-765-4532,11:23 AM 11/4/2009

Save the file in the C:DATA directory

As you can see, the flat file contains comma delimited information about customers, including their ids, names, points of contact, and associated contact information.

Create the Project

Update: November 30, 2009 : I posted the completed code for this project. You can download it here.

To create a .NET Assembly Connector use the Business Data Connectivity Model project type in Visual Studio 2010. Follow these steps to create the .NET Assembly Connector.

Open Visual Studio 2010 Beta 2
Click File, select New, select Project
In the Installed Templates section expand Visual C#, expand SharePoint, and select 2010
Select the Business Data Connectivity Model project type
In the Name textbox enter FlatFileBDCModel
\n $\"Creating$

6. Click OK
\n 7. Specify the SharePoint site where you would like to deploy and debug the project
\n $\"Set$
\n 8. Click Finish

Project Inventory

Before customizing the project, let’s take a moment to understand the files in it. Here you can see all the files in the Solution Explorer:

$\"BCS$

The following table describes what the numbered elements in the image above are used for.

\n\n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n

Element # In Screenshot Above	Description
1	References to the SharePoint assemblies are automatically added to the project.
2	A feature containing the BDC Model and .NET Assembly Connector.
3	A package (WSP) containing the feature and supporting files.
4	The BDC Model which defines the data source, how to connect to it, how to query it, and what type of information it returns.
5	A .NET class defining an entity the BDC Model returns.
6	A .NET class containing the code used to connect to the data source, query it, and return the entities it contains.

Defining the Entity

Before creating a BDC Model which defines the data source, how to connect to it, how to query it, and what type of information it returns, an entity must be defined. As mentioned in the table above, the Entity1.cs file defines an entity the BDC Model returns. The next step is to create an entity which maps to the data in the flat-file-data-source.txt file. To create the entity follow these steps:

In the Solution Explorer, right click Entity1.cs and select Rename
Rename the file FlatFileEntity.cs
Click Yes
In the Solution Explorer, right click FlatFileEntity.cs and select Open
Delete all the code inside the FlatFileEntity class

Next, create properties in the FlatFileEntity class to map to the data in the flat-file-data-source.txt file. Do this by adding the following code inside the FlatFileEntity class\n

public string ID { get; set; }
public string Company { get; set; }
public string FirstName { get; set; }
public string LastName { get; set; }
public string Address { get; set; }
public string City { get; set; }
public string State { get; set; }
public string ZipCode { get; set; }
public string Phone { get; set; }
public DateTime LastUpdated { get; set; }

Save the FlatFileEntity.cs class

The completed class looks like this after the properties are added:

using System;
using System.Collections.Generic;
using System.Linq;
using System.Text;

namespace FlatFileBCSModel.BdcModel1
{
    public partial class FlatFileEntity
    {
        public string ID { get; set; }
        public string Company { get; set; }
        public string FirstName { get; set; }
        public string LastName { get; set; }
        public string Address { get; set; }
        public string City { get; set; }
        public string State { get; set; }
        public string ZipCode { get; set; }
        public string Phone { get; set; }
        public DateTime LastUpdated { get; set; }
    }
}

Defining the Entity Service Class

Once the entity is defined, create the entity service class which queries the data source (flat-file-data-source.txt) and returns entities. The entity service class defines the finder and specific finder methods used to return entities from the data source. The ReadList() method defines the finder method for the BDC Model. The finder method is responsible for returning all the entities in the data source. This method returns an IEnumerable generic collection of entities. In this example the ReadList method returns an IEnumerable collection of FlatFileEntity objects (the entity class, created above).

The ReadItem(string id) method defines the specific finder method for the BDC Model. The specific finder method is responsible for returning a single entity from the data source. The specific finder method returns an object representing the entity. The id parameter passed into the ReadItem(string id) method is used to query the entities in the data source and return the entity whose identifier matches the parameter. In this example the ReadItem(string id) method returns a FlatFileEntity object (the entity class, created above).

To create the entity service class follow these steps:

In the Solution Explorer, right click Entity1Service.cs and select Rename
Rename the Entity to FlatFileEntityService.cs
Click Yes
In the Solution Explorer, right click FlatFileEntityService.cs and select Open
Add a using statement to the FlatFileEntityService.cs file to support file IO with the flat-file-data-source.txt file.\n
\n
```
using System.IO;
```
\n
\n

Next, create a method to return entities from the flat-file-data-source.txt file. This method opens the text file, iterates through each row of data, parses the data, creates an instance of the FlatFileEntity object for each row, sets the properties accordingly, adds the FlatFileEntity object to the IEnumerable generic collection, and finally returns the entire collection. Essentially this method returns strongly typed objects representing the data in the flat-file-data-source.txt file. To create this method add the following code to the FlatFileEntityService class.\n

public static List GetAllEntities()
{
    List flatFileEntityList = new List();

    TextReader textReader = new StreamReader(@\"c:dataflat-file-data-source.txt\");

    string row;

    while ((row = textReader.ReadLine()) != null)
    {
        FlatFileEntity flatFileEntity = new FlatFileEntity();

        string[] entityData = row.Split(',');

        flatFileEntity.ID = entityData[0];
        flatFileEntity.Company = entityData[1];
        flatFileEntity.FirstName = entityData[2];
        flatFileEntity.LastName = entityData[3];
        flatFileEntity.Address = entityData[4];
        flatFileEntity.City = entityData[5];
        flatFileEntity.State = entityData[6];
        flatFileEntity.ZipCode = entityData[7];
        flatFileEntity.Phone = entityData[8];
        flatFileEntity.LastUpdated = DateTime.Parse(entityData[9]);
        flatFileEntityList.Add(flatFileEntity);
    }

    textReader.Close();

    return flatFileEntityList;
}

Next, create the finder method. To do so first locate the ReadList() method and delete the sample code inside it.
Then add the following code inside the ReadList() method. This code uses the GetAllEntities method to return all the entities in the flat-file-data-source.txt file.\n
\n
```
return GetAllEntities().ToArray();
```
\n
\n

Next, create the specific finder method. To do so first locate the ReadItem(string id) method and delete the sample code inside it.
Then add the following code inside the ReadItem(string id)method. This code returns the entity in the flat-file-data-source.txt file whose identifier matches the id parameter passed into the method.

foreach (FlatFileEntity entity in GetAllEntities())
{
    if (entity.ID == id)
    {
        return entity;
    }
}

return null;

Save the FlatFileEntity.cs class

The completed class looks like this:

using System;
using System.Collections.Generic;
using System.Linq;
using System.Text;
using System.IO;

namespace FlatFileBCSModel.BdcModel1
{
    public class FlatFileEntityService
    {
        public static FlatFileEntity ReadItem(string id)
        {
            foreach (FlatFileEntity entity in GetAllEntities())
            {
                if (entity.ID == id)
                    return entity;
            }
            return null;
        }

        public static IEnumerable ReadList()
        {
            return GetAllEntities().ToArray();
        }

        public static List GetAllEntities()
        {
            List flatFileEntityList = new List();

            TextReader textReader = new StreamReader(@\"c:dataflat-file-data-source.txt\");

            string row;

            while ((row = textReader.ReadLine()) != null)
            {
                FlatFileEntity flatFileEntity = new FlatFileEntity();

                string[] entityData = row.Split(',');

                flatFileEntity.ID = entityData[0];
                flatFileEntity.Company = entityData[1];
                flatFileEntity.FirstName = entityData[2];
                flatFileEntity.LastName = entityData[3];
                flatFileEntity.Address = entityData[4];
                flatFileEntity.City = entityData[5];
                flatFileEntity.State = entityData[6];
                flatFileEntity.ZipCode = entityData[7];
                flatFileEntity.Phone = entityData[8];
                flatFileEntity.LastUpdated = DateTime.Parse(entityData[9]);
                flatFileEntityList.Add(flatFileEntity);
            }

            textReader.Close();

            return flatFileEntityList;
        }
    }
}

\n
\nAs previously mentioned, the assembly which is created when this code is compiled is referred to as a .NET Assembly Connector.

After the entity and entity service are defined it is possible to create the BDC Model which defines how to connect to the data source, how to query it, and what type of information it returns. The BDC Explorer and the BDC Model designer are used to define the BDC Model. Both of these new VS 2010 components are described below.

BDC Explorer

Visual Studio 2010 now includes the BDC Explorer (shown below) which may be used to create the BDC Model.

$\"BDC$

The BDC Explorer works with the Properties window to allow you to inspect and modify the BDC Model. The screenshot below demonstrates this. When Identifier 1 is selected in the BDC Explorer the corresponding properties are displayed in the Properties window.

$\"BDC$

BDC Model Designer

Visual Studio 2010 now includes the BDC Model Designer (shown below) which is used to create the BDC Model.

$\"BDC$

The BDC Model Designer works just like the BDC Explorer with the Properties window.

Defining the BDC Model

In this series of steps the mappings between the .NET Assembly Connector and the BDC are defined.

To begin, open the BDC Explorer by right clicking on the BDCModel1.bdcm file in the Solution Explorer and selecting Open. You will notice the BDC Model Designer opens.
Then, in the View Menu, select Other Windows and select BDC Explorer.
The first thing to do is to rename the BDC Model. To rename the BDC Model, select BDCModel1 in the BDC Explorer. There are many nodes in the BDC Explorer named BDCModel1 by default, select the highlighted one shown below.
\n $\"BDC$
In the Properties window change the Name property to FlatFileBDCModel
The next thing to do is to rename the LOB System. To rename the LOB System, select BDCModel1 in the BDC Explorer. There are many nodes in the BDC Explorer named BDCModel1 by default, select the highlighted one shown below.
\n $\"LOB$
In the Properties window change the Name property to FlatFileLOBSystem
The next thing to do is to rename the LOB System Instance. To rename the LOB System Instance, select BDCModel1 in the BDC Explorer. There are many nodes in the BDC Explorer named BDCModel1 by default, select the highlighted one shown below.
\n $\"LOB$
In the Properties window change the Name property to FlatFileLOBSystemInstance
The ShowInSearchUI property on the FlatFileLOBSystemInstance must be set to allow the FlatFileLOBSystemInstance to be crawled and searched by the SharePoint search service. This property does not have to be set if the LOBSystemInstance will not be crawled or searched. To set the ShowInSearchUI property on the FlatFileLOBSystemInstance click the FlatFileLOBSystemInstance node in the BDC Explorer.
Then, in the Properties window click the button in the Custom Properties row.
In the Properties Editor, add the ShowInSearchUI property, with a data type of System.String and a value of x.
\n $\"ShowInSearchUI$
Click OK
\n
\n After the LOB System and LOB System Instance are configured the Entity and its properties are configured.
\n
\n
Rename the entity in the BDC Model to match the entity defined in the .NET Assembly Connector. To do this, select Entity1 in the BDC Explorer.
In the Properties window change the Name property to FlatFileEntity
\n
\n

After the Entity and its properties are configured the methods and parameters are configured.
\n

The RootFinder property on the finder method must be set to specify the finder method used to enumerate the items to crawl. This property does not have to be set if the finder method is not used for crawling. To set the RootFinder property on the finder method click the ReadList node in the BDC Explorer.
Then, in the Properties window click the button in the Custom Properties row.
In the Properties Editor, add the RootFinder property, with a data type of System.String and a value of x.
\n $\"RootFinder$
The next step is to set the identifier for finder method return parameter in the entity. To do so first select the Identifier1 node under the finder method return parameter for the FlatFileEntity (highlighted below).
\n $\"Finder$
Then, in the Properties window change the Name property to ID
Next, set the identifier for the specific finder return parameter in the entity. To do so first select the Identifier1 node under the specific finder method return parameter for the FlatFileEntity (highlighted below).
\n $\"Specific$
Then, in the Properties window change the Name property to ID
Finally, set the identifier for the specific finder input parameter in the entity. To do so first select the Identifier1 node under the specific finder method for the FlatFileEntity (highlighted below).
\n $\"Specific$
Then, in the Properties window change the Name property to ID
In the BDC Model Designer, right click Identifier1 and select Rename
\n $\"Rename$
Rename the Identifier to ID
\n $\"Renamed$
\n
\n After the Identifier is configured the remaining parameters are configured
\n
\n
First, remove the message parameters since they are not needed. To remove the message parameter from the finder method select the message node in the BDC Explorer, right click, and select Delete.
\n $\"Delete$
To remove the message parameter from the specific finder method select the message node in the BDC Explorer, right click, and select Delete.
\n $\"Delete$
Next, add the parameters which map to the data in the flat-file-data-source.txt file. Use steps 29-31 to add the parameters listed in the table below.
\n

Parameter Name	Data Type
Company	System.String
FirstName	System.String
LastName	System.String
Address	System.String
City	System.String
State	System.String
ZipCode	System.String
Phone	System.String
LastUpdated	System.DateTime

In the BDC Explorer, right click Entity1 and select Add Type Descriptor
\n $\"Add$
In the Properties window change the Name property to match the name of the property you are adding from the table above.
In the Properties window change the Type Name property to match the data type of the property you are adding from the table above.
\n
\n Once all the parameters are added the BDC Model looks like this in the BDC Explorer:
\n
\n $\"Parameters$
\n
Next, copy the parameters from the finder method to the specific finder method. To do this perform steps 33-35 for each return parameter in the finder method.
\n
\n Note: The ID parameter is already configured and does not need to be copied from the finder method to the specific finder method.
\n
In the BDC Explorer select the parameter to copy, right click, and select Copy.
\n $\"Copy$
In the BDC Explorer select the Entity1 node under the returnParameter node for the specific finder method, right click, and select Paste.
\n $\"Paste$
\n
\n After all the parameters are copied the BDC Model looks like this in the BDC Explorer:
\n
\n $\"Return$
\n
Next, edit the data type of the LastUpdated return parameter in the specific finder method. To do this, select the LastUpdated return parameter for the specific finder method.
\n
\n $\"LastUpdated$
\n
In the Properties window change the Type Name property to System.String
\n
\n After the remaining parameters are configured the finder method instance properties are configured
\n
\n Configuring method instance properties may be done with the BDC Method Details window which Visual Studio 2010 now includes. Selecting a method in the BDC Designer displays the corresponding method instance in the BDC Method Details window, as seen in the screenshot below.
\n
\n $\"BDC$
\n
\n The BDC Method Details window works just like the BDC Explorer and the BDC Model Designer do with the Properties window.
\n
The RootFinder property on the finder method instance must be set to specify the finder method instance used to enumerate the items to crawl. This property does not have to be set if the finder method instance is not used for crawling. To set the RootFinder property on the finder method instance first click the ReadList node in the BDC Method Details window (highlighted in the screenshot below).
\n $\"ReadList$
Then, in the Properties window click the button in the Custom Properties row.
In the Properties Editor, add the RootFinder property, with a data type of System.String and a value of x.
\n $\"RootFinder$
The LastModifiedTimeStampField property on the finder method instance is set for two reasons.
\n
\n 1. So search results will display the last time the data was updated
\n 2. So the search service knows if the data has been changed when executing incremental crawls.
\n
\n This property does not have to be set if the finder method instance is not used for crawling. To set the RootFinder property on the finder method instance first click the ReadList node in the BDC Method Details window (highlighted in the screenshot below).
\n $\"ReadList$
Then, in the Properties window click the button in the Custom Properties row.
\n
In the Properties Editor, add the LastModifiedTimeStampField property, with a data type of System.String and a value of LastUpdated
\n $\"LastModifiedTimeStampField$
\n
Quick Cleanup
\n
In the Solution Explorer right click the FlatFileEntityService.cs class and select Open.
The designer sometimes adds some unneeded code to the class that must be removed. Locate the following code and delete it. If you cannot locate this code then move on to the next step.

public static FlatFileEntity ReadItem(string id)
{
    throw new System.NotImplementedException();
}

Deploy and Test

Deploying and testing the .NET Assembly Connector is a piece of cake!

Deploy

In the Build menu, select Deploy Solution.
\n
\n At this point Visual Studio 2010 compiles the .NET Assembly Connector code and packages the BDC Model and the feature which deploys both of these items into a WSP. The WSP is deployed to the SharePoint web site specified when the project was created. The feature in the WSP is automatically activated to register the External Content Type associated with the .NET Assembly Connector.

Test

Open the SharePoint web site where Visual Studio 2010 deployed the WSP.
Log in as a user who has the permission to create lists.
Click the Site Actions menu
Select View All Site Content
Click Create
In the Filter By section of the page click Lists
Select External List
\n $\"Create$
Click the Create button
In the Name textbox enter Flat File Data
Click the button to browse the external content types.
\n $\"Create$
Select the FlatFileLOBSystemInstance in the External Content Type Picker
\n $\"External$
Click OK
Click Create
View the data from the flat-file-data-source.txt file in the external list!
\n $\"Flat$

Where’s the XML?

I’m sure you noticed the lack of XML during this blog post. If you are curious where the XML is that defines the BDC Model follow these steps:

In the Solution Explorer, right click the BdcModel1.bdcm file and select Open With…
\n $\"View$
In the Open With dialog select XML Editor
Click OK

The complete BDC Model XML looks like this:

xml version=\"1.0\" encoding=\"utf-8\"?>
<Model xmlns:xsi=\"http://www.w3.org/2001/XMLSchema-instance\" xmlns:xsd=\"http://www.w3.org/2001/XMLSchema\" xmlns=\"http://schemas.microsoft.com/windows/2007/BusinessDataCatalog\" Name=\"FlatFileBDCModel\">
  <LobSystems>
    <LobSystem Name=\"FlatFileLOBSystem\" Type=\"DotNetAssembly\">
      <LobSystemInstances>
        <LobSystemInstance Name=\"FlatFileLOBSystemInstance\" DefaultDisplayName=\"Customers\">
          <Properties>
            <Property Name=\"ShowInSearchUI\" Type=\"System.String\">xProperty>Properties>LobSystemInstance>
      LobSystemInstances>
      <Entities>
        <Entity Name=\"FlatFileEntity\" Namespace=\"FlatFileBDCModel.BdcModel1\" EstimatedInstanceCount=\"1000\" Version=\"1.0.0.46\">
          <Properties>
            <Property Name=\"Class\" Type=\"System.String\">FlatFileBDCModel.BdcModel1.FlatFileEntityService, FlatFileLOBSystemProperty>
          Properties>
          <Identifiers>
            <Identifier Name=\"ID\" TypeName=\"System.String\" />
          Identifiers>
          <Methods>
            <Method Name=\"ReadList\">
              <Properties>
                <Property Name=\"RootFinder\" Type=\"System.String\">xProperty>Properties>
              <Parameters>
                <Parameter Direction=\"Return\" Name=\"returnParameter\">
                  <TypeDescriptor TypeName=\"System.Collections.Generic.IEnumerable`1[[FlatFileBDCModel.BdcModel1.FlatFileEntity, FlatFileLOBSystem]]\" IsCollection=\"true\" Name=\"Entity1List\" DefaultDisplayName=\"2\">
                    <TypeDescriptors>
                      <TypeDescriptor TypeName=\"FlatFileBDCModel.BdcModel1.FlatFileEntity, FlatFileLOBSystem\" Name=\"Entity1\" DefaultDisplayName=\"1\">
                        <TypeDescriptors>
                          <TypeDescriptor TypeName=\"System.String\" IdentifierName=\"ID\" Name=\"ID\" />
                          <TypeDescriptor Name=\"Company\" TypeName=\"System.String\" />
                          <TypeDescriptor Name=\"FirstName\" TypeName=\"System.String\" />
                          <TypeDescriptor Name=\"LastName\" TypeName=\"System.String\" />
                          <TypeDescriptor Name=\"Address\" TypeName=\"System.String\" />
                          <TypeDescriptor Name=\"City\" TypeName=\"System.String\" />
                          <TypeDescriptor Name=\"State\" TypeName=\"System.String\" />
                          <TypeDescriptor Name=\"ZipCode\" TypeName=\"System.String\" />
                          <TypeDescriptor Name=\"Phone\" TypeName=\"System.String\" />
                          <TypeDescriptor Name=\"LastUpdated\" TypeName=\"System.DateTime\" />TypeDescriptors>
                      TypeDescriptor>
                    TypeDescriptors>
                  TypeDescriptor>
                Parameter>
              Parameters>
              <MethodInstances>
                <MethodInstance Type=\"Finder\" ReturnParameterName=\"returnParameter\" Default=\"true\" Name=\"ReadList\" DefaultDisplayName=\"Entity1 List\">
                  <Properties>
                    <Property Name=\"RootFinder\" Type=\"System.String\">xProperty>
                    <Property Name=\"LastModifiedTimeStampField\" Type=\"System.String\">LastUpdatedProperty>Properties>
                  MethodInstance>
              MethodInstances>
            Method>
            <Method Name=\"ReadItem\">
              <Parameters>
                <Parameter Direction=\"In\" Name=\"id\">
                  <TypeDescriptor TypeName=\"System.String\" IdentifierName=\"ID\" Name=\"ID\" />
                Parameter>
                <Parameter Direction=\"Return\" Name=\"returnParameter\">
                  <TypeDescriptor TypeName=\"FlatFileBDCModel.BdcModel1.FlatFileEntity, FlatFileLOBSystem\" Name=\"Entity1\" DefaultDisplayName=\"3\">
                    <TypeDescriptors>
                      <TypeDescriptor TypeName=\"System.String\" IdentifierName=\"ID\" Name=\"ID\" />
                      <TypeDescriptor Name=\"Address\" TypeName=\"System.String\" />
                      <TypeDescriptor Name=\"City\" TypeName=\"System.String\" />
                      <TypeDescriptor Name=\"Company\" TypeName=\"System.String\" />
                      <TypeDescriptor Name=\"FirstName\" TypeName=\"System.String\" />
                      <TypeDescriptor Name=\"LastName\" TypeName=\"System.String\" />
                      <TypeDescriptor Name=\"LastUpdated\" TypeName=\"System.String\" />
                      <TypeDescriptor Name=\"Phone\" TypeName=\"System.String\" />
                      <TypeDescriptor Name=\"State\" TypeName=\"System.String\" />
                      <TypeDescriptor Name=\"ZipCode\" TypeName=\"System.String\" />TypeDescriptors>
                  TypeDescriptor>
                Parameter>
              Parameters>
              <MethodInstances>
                <MethodInstance Type=\"SpecificFinder\" ReturnParameterName=\"returnParameter\" Default=\"true\" Name=\"ReadItem\" DefaultDisplayName=\"Read Entity1\" />
              MethodInstances>
            Method>
          Methods>
        Entity>
      Entities>
    LobSystem>
  LobSystems>
Model>

\n
\n

Stay Tuned!

Check back tomorrow for part two in this series which demonstrates how to register an external content type with the SharePoint search service to make the data searchable.

","excerpt":"","date":"2009-11-06T00:29:01","modified":"2013-07-01T19:54:22","author":"Todd Baginski","authorSlug":"todd","categories":[{"id":100,"name":"BCS","slug":"bcs","count":26},{"id":46,"name":"Most Popular","slug":"most-popular","count":19},{"id":97,"name":"SharePoint","slug":"sharepoint","count":58}],"tags":[{"id":27,"name":".NET Assembly Connector","slug":"net-assembly-connector","count":1},{"id":4,"name":"BDC","slug":"bdc","count":20},{"id":10,"name":"Custom Development","slug":"custom-development","count":87},{"id":5,"name":"Helpful Code","slug":"helpful-code","count":70},{"id":6,"name":"HOW TO: SharePoint","slug":"how-to-sharepoint","count":31},{"id":7,"name":"SharePoint","slug":"sharepoint","count":85},{"id":26,"name":"SharePoint 2010","slug":"sharepoint-2010","count":32}],"featuredImage":"/blog/uploads/2011/05/IMG_3359-e1306876093169.jpg","status":"publish"}],"total":1,"totalPages":1,"currentPage":1,"archiveType":"tag","archiveName":".NET Assembly Connector","archiveSlug":"net-assembly-connector","archivePathSegments":"net-assembly-connector","categories":[{"id":146,"name":"AI","slug":"ai","count":1},{"id":90,"name":"Blog","slug":"blog","count":2},{"id":103,"name":"Cloud","slug":"cloud","count":68},{"id":102,"name":"Community","slug":"community","count":41},{"id":110,"name":"GitHub","slug":"github","count":4},{"id":139,"name":"Lacrosse","slug":"lacrosse","count":1},{"id":96,"name":"Mobile","slug":"mobile","count":62},{"id":46,"name":"Most Popular","slug":"most-popular","count":19},{"id":88,"name":"Office","slug":"office","count":21},{"id":104,"name":"Office 365","slug":"office-365","count":80},{"id":89,"name":"Operations","slug":"operations","count":13},{"id":121,"name":"PowerApps","slug":"powerapps","count":57},{"id":87,"name":"Publications","slug":"publications","count":17},{"id":97,"name":"SharePoint","slug":"sharepoint","count":58},{"id":84,"name":"SharePoint 2007","slug":"sharepoint-2007","count":22},{"id":98,"name":"SharePoint 2010","slug":"sharepoint-2010","count":40},{"id":99,"name":"SharePoint 2013","slug":"sharepoint-2013","count":20},{"id":106,"name":"SharePoint 2016","slug":"sharepoint-2016","count":6},{"id":118,"name":"SharePoint Framework","slug":"sharepoint-framework","count":1},{"id":83,"name":"Speaking Engagements","slug":"speaking-engagements","count":41},{"id":119,"name":"SPFx","slug":"spfx","count":1},{"id":85,"name":"SPS Events Mobile","slug":"sps-events-mobile","count":4},{"id":116,"name":"Teams","slug":"teams","count":3},{"id":1,"name":"Uncategorized","slug":"uncategorized","count":3},{"id":86,"name":"Windows 8","slug":"windows-8","count":7},{"id":101,"name":"Azure","slug":"azure","count":24},{"id":100,"name":"BCS","slug":"bcs","count":26},{"id":132,"name":"CDS","slug":"cds","count":3},{"id":120,"name":"Flow","slug":"flow","count":18}],"tags":[{"id":10,"name":"Custom Development","slug":"custom-development","count":87},{"id":7,"name":"SharePoint","slug":"sharepoint","count":85},{"id":5,"name":"Helpful Code","slug":"helpful-code","count":70},{"id":54,"name":"Mobile","slug":"mobile","count":66},{"id":45,"name":"O365","slug":"o365","count":65},{"id":112,"name":"PowerApps","slug":"powerapps","count":56},{"id":42,"name":"Cloud","slug":"cloud","count":46},{"id":122,"name":"HOW TO: PowerApps","slug":"how-to-powerapps","count":38},{"id":26,"name":"SharePoint 2010","slug":"sharepoint-2010","count":32},{"id":6,"name":"HOW TO: SharePoint","slug":"how-to-sharepoint","count":31},{"id":57,"name":"Mobility","slug":"mobility","count":28},{"id":3,"name":"Conferences","slug":"conferences","count":27},{"id":41,"name":"Azure","slug":"azure","count":21},{"id":4,"name":"BDC","slug":"bdc","count":20},{"id":40,"name":"Windows Phone 7","slug":"windows-phone-7","count":17},{"id":58,"name":"Android","slug":"android","count":14},{"id":60,"name":"iPad","slug":"ipad","count":14},{"id":68,"name":"SharePoint 2013","slug":"sharepoint-2013","count":14},{"id":23,"name":"Conference Materials","slug":"conference-materials","count":13},{"id":59,"name":"iPhone","slug":"iphone","count":13},{"id":113,"name":"Flow","slug":"flow","count":12},{"id":43,"name":"SharePoint Online","slug":"sharepoint-online","count":12},{"id":28,"name":"BCS","slug":"bcs","count":11},{"id":80,"name":"Windows Phone 8","slug":"windows-phone-8","count":8},{"id":61,"name":"iOS","slug":"ios","count":7},{"id":38,"name":"Magazine Articles","slug":"magazine-articles","count":7},{"id":74,"name":"SharePoint Apps","slug":"sharepoint-apps","count":7},{"id":9,"name":"Workflow","slug":"workflow","count":7},{"id":22,"name":"Development Utilities","slug":"development-utilities","count":6},{"id":37,"name":"MSDN","slug":"msdn","count":6},{"id":25,"name":"Silverlight","slug":"silverlight","count":6},{"id":8,"name":"Virtual Environments","slug":"virtual-environments","count":5},{"id":30,"name":"External Content Types","slug":"external-content-types","count":4},{"id":72,"name":"SharePoint Hosted","slug":"sharepoint-hosted","count":4},{"id":13,"name":"Site Definitions","slug":"site-definitions","count":4},{"id":12,"name":"Site Templates","slug":"site-templates","count":4},{"id":44,"name":"SPO","slug":"spo","count":4},{"id":33,"name":"Visual Studio","slug":"visual-studio","count":4},{"id":55,"name":"WCM","slug":"wcm","count":4},{"id":128,"name":"CDS","slug":"cds","count":3},{"id":127,"name":"Ignite","slug":"ignite","count":3},{"id":115,"name":"SPFx","slug":"spfx","count":3},{"id":14,"name":"SSO","slug":"sso","count":3},{"id":117,"name":"Teams","slug":"teams","count":3},{"id":24,"name":"Hyper-V","slug":"hyper-v","count":2},{"id":126,"name":"IoT","slug":"iot","count":2},{"id":76,"name":"Mapping","slug":"mapping","count":2},{"id":56,"name":"Outlook","slug":"outlook","count":2},{"id":32,"name":"Sandbox","slug":"sandbox","count":2},{"id":21,"name":"SharePoint Certified Architect","slug":"sharepoint-certified-architect","count":2},{"id":11,"name":"SharePoint Designer","slug":"sharepoint-designer","count":2},{"id":108,"name":"SharePoint Framework","slug":"sharepoint-framework","count":2},{"id":34,"name":"Visual Web Parts","slug":"visual-web-parts","count":2},{"id":91,"name":"Xamarin","slug":"xamarin","count":2},{"id":27,"name":".NET Assembly Connector","slug":"net-assembly-connector","count":1},{"id":50,"name":"Access Services","slug":"access-services","count":1},{"id":35,"name":"Aptillon","slug":"aptillon","count":1},{"id":36,"name":"BCS FAQ","slug":"bcs-faq","count":1},{"id":39,"name":"Books","slug":"books","count":1},{"id":148,"name":"Claude","slug":"claude","count":1},{"id":131,"name":"Common Data Service","slug":"common-data-service","count":1},{"id":82,"name":"Community","slug":"community","count":1},{"id":52,"name":"Composites","slug":"composites","count":1},{"id":123,"name":"Containers","slug":"containers","count":1},{"id":92,"name":"Cordova","slug":"cordova","count":1},{"id":65,"name":"CSS3","slug":"css3","count":1},{"id":140,"name":"DIY","slug":"diy","count":1},{"id":124,"name":"Docker","slug":"docker","count":1},{"id":133,"name":"Flows","slug":"flows","count":1},{"id":75,"name":"Geolocation","slug":"geolocation","count":1},{"id":111,"name":"GitHub","slug":"github","count":1},{"id":125,"name":"HOW TO: Flow","slug":"how-to-flow","count":1},{"id":62,"name":"HTML5","slug":"html5","count":1},{"id":49,"name":"InfoPath Forms Services","slug":"infopath-forms-services","count":1},{"id":64,"name":"JavaScript","slug":"javascript","count":1},{"id":63,"name":"JQuery","slug":"jquery","count":1},{"id":66,"name":"JQuery Mobile","slug":"jquery-mobile","count":1},{"id":31,"name":"Lists","slug":"lists","count":1},{"id":69,"name":"Mashups","slug":"mashups","count":1},{"id":19,"name":"MCA","slug":"mca","count":1},{"id":18,"name":"MCM","slug":"mcm","count":1},{"id":79,"name":"Nofifications","slug":"nofifications","count":1},{"id":105,"name":"Office","slug":"office","count":1},{"id":95,"name":"Office Add-ins","slug":"office-add-ins","count":1},{"id":78,"name":"Office Web Apps Server","slug":"office-web-apps-server","count":1},{"id":130,"name":"Operations","slug":"operations","count":1},{"id":129,"name":"PowerShell","slug":"powershell","count":1},{"id":15,"name":"QuickLaunch","slug":"quicklaunch","count":1},{"id":29,"name":"Search","slug":"search","count":1},{"id":107,"name":"SharePoint 2016","slug":"sharepoint-2016","count":1},{"id":71,"name":"SharePoint App","slug":"sharepoint-app","count":1},{"id":20,"name":"SharePoint Certified Master","slug":"sharepoint-certified-master","count":1},{"id":17,"name":"SharePoint Master Certification","slug":"sharepoint-master-certification","count":1},{"id":109,"name":"SharePoint Mobile App","slug":"sharepoint-mobile-app","count":1},{"id":77,"name":"SharePoint Saturday","slug":"sharepoint-saturday","count":1},{"id":73,"name":"SP APP","slug":"sp-app","count":1},{"id":70,"name":"SPAPP","slug":"spapp","count":1},{"id":81,"name":"SPS Events","slug":"sps-events","count":1},{"id":67,"name":"SSS","slug":"sss","count":1},{"id":16,"name":"Top Navigation","slug":"top-navigation","count":1},{"id":94,"name":"Training","slug":"training","count":1},{"id":134,"name":"Twitter","slug":"twitter","count":1},{"id":93,"name":"Universal","slug":"universal","count":1},{"id":114,"name":"Windows Phone","slug":"windows-phone","count":1},{"id":51,"name":"Workflows","slug":"workflows","count":1},{"id":53,"name":"WP7; SharePoint; SharePoint 2010; Social; Mobile","slug":"wp7-sharepoint-sharepoint-2010-social-mobile","count":1},{"id":147,"name":"XCode","slug":"xcode","count":1}],"recentPosts":[{"id":2222,"slug":"how-to-reauthenticate-claude-in-xcode","title":"HOW TO: Reauthenticate Claude in XCode","content":"\n

If you set up XCode to integrate with Claude you may find the OAuth token expires and the chat in XCode cannot communicate with Claude, then you see this error message.

OAuth token has expired. Please obtain a new token or refresh your existing token.

\n\n\n\n

\n\n\n\n

To resolve this issue quickly open XCode Settings > Intelligence.

\n\n\n\n

Click the ellipses next to your account, and select Sign Out.

\n\n\n\n

\n\n\n\n

Click the ellipses again and select Sign In.

\n\n\n\n

This will open a web browser where you can sign in and click Authorize.

\n\n\n\n

Restart XCode.

\n\n\n\n

\n\n\n\n

Happy coding!

\n","excerpt":"

If you set up XCode to integrate with Claude you may find the OAUth token expires and the chat in XCode cannot communicate with Claude. Here's how to fix it.

","date":"2026-04-01T21:22:55","modified":"2026-04-01T21:22:57","author":"Todd Baginski","authorSlug":"todd","categories":[{"id":146,"name":"AI","slug":"ai","count":1}],"tags":[{"id":148,"name":"Claude","slug":"claude","count":1},{"id":10,"name":"Custom Development","slug":"custom-development","count":87},{"id":147,"name":"XCode","slug":"xcode","count":1}],"featuredImage":"/blog/uploads/2026/04/xcode-claude.png","status":"publish"},{"id":2165,"slug":"how-to-disable-turn-off-a-power-platform-managed-environment","title":"HOW TO: Disable/Turn Off a Power Platform Managed Environment","content":"\n

What do you do if you accidentally enabled a Managed Environment in the Power Platform and you want to make the Environment non-Managed again? There is no way in the Power Platform Admin Center to Disable / Turn Off a Managed Environment, you can only Enable or Delete Managed Environments in the Admin Center. To Disable / Turn Off a Managed Environment, and go back to a non-Managed Environment, you must use PowerShell. Here's how to do it:

\n\n\n\n

Open a PowerShell prompt as Administrator.

\n\n\n\n

Install PowerShell

\n\n\n\n

Install-Module -Name Microsoft.PowerApps.Administration.PowerShell

\n\n\n\n

Log in with an account that has permissions to administer Environments. The following command will open an authentication prompt. The prompt supports MFA.

\n\n\n\n

Add-PowerAppsAccount -Endpoint prod

\n\n\n\n

Run this code that sets protectionLevel to Basic, which turns an Environment from Managed to non-Managed.

\n\n\n\n

$UpdatedGovernanceConfiguration = [pscustomobject]@{ protectionLevel = \"Basic\" }

\n\n\n\n

Run this command to apply the changes to the Environment you want to convert from Managed to non-Managed. Make sure to replace the Environment Id accordingly.

\n\n\n\n

Set-AdminPowerAppEnvironmentGovernanceConfiguration -EnvironmentName -UpdatedGovernanceConfiguration $UpdatedGovernanceConfiguration

\n\n\n\n

Here's what it all looks like:

\n\n\n\n

\n\n\n\n

Here's the Microsoft documentation that describes part of this process.

\n\n\n\n

https://learn.microsoft.com/en-us/power-platform/admin/managed-environment-enable#disable-managed-environments-using-powershell

\n\n\n\n

\n","excerpt":"

What do you do if you accidentally enabled a Managed Environment in the Power Platform and you want to make the Environment non-Managed again?

","date":"2024-10-15T16:47:48","modified":"2024-10-15T16:47:49","author":"Todd Baginski","authorSlug":"todd","categories":[{"id":103,"name":"Cloud","slug":"cloud","count":68},{"id":120,"name":"Flow","slug":"flow","count":18},{"id":104,"name":"Office 365","slug":"office-365","count":80},{"id":121,"name":"PowerApps","slug":"powerapps","count":57}],"tags":[{"id":42,"name":"Cloud","slug":"cloud","count":46},{"id":10,"name":"Custom Development","slug":"custom-development","count":87},{"id":5,"name":"Helpful Code","slug":"helpful-code","count":70},{"id":122,"name":"HOW TO: PowerApps","slug":"how-to-powerapps","count":38},{"id":54,"name":"Mobile","slug":"mobile","count":66},{"id":112,"name":"PowerApps","slug":"powerapps","count":56}],"featuredImage":"/blog/uploads/2024/10/sunset-ocean.jpg","status":"publish"},{"id":2143,"slug":"how-to-make-a-diy-lacrosse-goal-transporter","title":"HOW TO: Make a DIY lacrosse goal transporter","content":"\n

There are several products on the market that make it easy to move your lacrosse goal. I investigated them and then created my own to save my yard, my back, and my money. An added bonus is you can store your goal on the transporter to keep it off the ground and free from dirt and moisture.

\n\n\n\n

This is especially helpful if you have ECD targets, a Smart Backstop shooting net, and a Lax Dog strapped to your goal, which makes it quite heavy! These are not affiliate links, I don't make any money off them. Just thought I'd share the links because we really enjoy these products.

\n\n\n\n

Hopefully this article helps out my brothers and sisters in the lax community.

\n\n\n\n

\n\n\n\n

Parts

\n\n\n\n

1 - 4x4x8' #2 Ground Contact Green pressure-treated timber - $10.30

\n\n\n\n

1 - 2x4x8' #2 Ground Contact Green pressure treated lumber - $3.89

\n\n\n\n

1 - 21\" #2 Ground Contact Green pressure-treated timber - $0.00 *

\n\n\n\n

19 - #9 2 1/2\" coated deck screws - $0.00 *

\n\n\n\n

2 - 5/8\" x 8\" galvanized lag screws - $3.39 (these become the wheel axles)

\n\n\n\n

2 - 8\" Pneumatic Utility Tire (no flat) - $20.57 (comes with plastic spacers - you could cut a small pipe to make a spacer too)

\n\n\n\n

* Already had these items in my shop from previous projects.

\n\n\n\n

Total: $38.15

\n\n\n\n

Instructions

\n\n\n\n

Lay the goal on top of the 4x4.

\n\n\n\n

Mark the 4x4 where you want to cut it. Leave a little room on the ends to install a stopper (scroll down to see the picture with the stopper) to prevent the goal from sliding off the end. I left about 2\" of space on either side of the goal.

\n\n\n\n

Cut the 4x4 to the length that makes sense for your goal. I went with 80\" for my 4x4.

\n\n\n\n

Mark the center of each end of the 4x4. Then use a 7/16\" (or the appropriate size bit that is small enough that the threads on the lag screw will still bite into the wood) drill bit to drill a hole as deep as the threads on your lag screw. The lag screws are the axles for the wheels. In my case I used a boring bit, and the hole was over 4\" deep. This is the most important step. If you drill this hole off-center or off-axis the tires will not be aligned properly. If the pressure treated wood is fresh and wet, this could be challenging. Take your time, get it right the first time.

\n\n\n\n

Use a large socket wrench to screw the lag screws into the 4x4 until all the threads are engaged. Don't put your wheel or spacer on yet. Leave them off so you can concentrate on screwing in the screw perfectly. This is the 2nd most important step. If you screw it in on an angle, the tires will not be aligned properly. This is not easy; you will need to put a lot of muscle into this.

\n\n\n\n

Use a large socket wrench to un-screw the lag screws from the 4x4 all the way. Be careful when you take out the lag screw, it could be quite hot from the friction.

\n\n\n\n

Lay the goal on top of the 4x4 and center it.

\n\n\n\n

This picture shows the pieces described in the next set of steps.

\n\n\n\n

\n\n\n\n

Cut some of the 21\" 2x4 to make little stoppers for top ends of the 4x4. You will do this 2 times, one for each end.

\n\n\n\n

Align the stopper on top of the 4x4 and drill holes in the 2x4 stopper you just made. Go all the way through so you mark the 4x4 with holes. Remove the stopper and finish drilling out the holes in the 4x4. You will do this 2 times, one for each end.

\n\n\n\n

Screw the stoppers to the 4x4 with the deck screws. You will do this 2 times, one for each end.

\n\n\n\n

Cut some 2x4 to make a brace for the goal posts to prevent the goal from sliding off the 4x4. I made my braces 8\" long. You will do this 2 times, one for each goal post.

\n\n\n\n

Align the brace on the side of the 4x4 and drill holes in the 2x4 braces you just made. Go all the way through so you mark the 4x4 with holes. Remove the brace and finish drilling out the holes in the 4x4. You will do this 2 times, one for each end.

\n\n\n\n

Screw the brace to the 4x4 with the deck screws. You will do this 2 times, one for each end.

\n\n\n\n

This picture shows the pieces described in the next set of steps.

\n\n\n\n

\n\n\n\n

Align the 2x4 in the middle of the 4x4 make the end flush to the edge of the 4x4. Drill holes in the 2x4 and go all the way through so you mark the 4x4 with holes. Remove the brace and finish drilling out the holes in the 4x4.

\n\n\n\n

Screw the 2x4 to the 4x4 with the deck screws.

\n\n\n\n

This picture shows the pieces described in the next set of steps.

\n\n\n\n

\n\n\n\n

Pass the lag screw through the wheel, add the spacer on the other side, then use the large socket wrench to tighten the screw. You will do this 2 times, one for each end.

\n\n\n\n

Walk around the back of your goal and grab the 2x4 and lift up the goal.

\n\n\n\n

\n\n\n\n

Now, add a little flair and make it easier to lift the 2x4 by adding a custom handle. This beauty was made by my Dad when he created our treehouse when I was a boy. It lives on today as part of our lacrosse transporter! I attached it with 2 deck screws.

\n\n\n\n

\n\n\n\n

Move your goal to a suitable location and rip some Gs!

\n\n\n\n

\n\n\n\n

Here are some more pictures that show everything from a few different angles.

\n\n\n\n

\n\n\n\n

\n\n\n\n

\n\n\n\n

\n\n\n\n

\n","excerpt":"

There are several products on the market that make it easy to move your lacrosse goal. I investigated them and then created my own to save my yard, my back, and my money.

","date":"2024-09-23T22:29:27","modified":"2024-11-20T16:48:07","author":"Todd Baginski","authorSlug":"todd","categories":[{"id":139,"name":"Lacrosse","slug":"lacrosse","count":1}],"tags":[{"id":140,"name":"DIY","slug":"diy","count":1}],"featuredImage":"/blog/uploads/2024/09/fi.jpg","status":"publish"},{"id":2117,"slug":"accelerate-development-with-the-catalog-for-power-platform","title":"Accelerate development with the Catalog for Power Platform","content":"\n

This video demonstrates how to accelerate development with the Catalog for Power Platform in both green field (creating a new app from scratch) and enhancement (taking an existing app and updating it) scenarios.

\n\n\n\n

In this video you will learn how to add Solutions to the Catalog and how to deploy them to Power Platform environments. You will also learn how to organize your Solutions and reusable components to enable quick app development and streamlined enhancements and maintenance.

\n\n\n\n

\n","excerpt":"

Learn how to accelerate development with the Catalog for Power Platform in both green field (creating a new app from scratch) and enhancement (taking an existing app and updating it) scenarios.

","date":"2023-05-25T13:30:00","modified":"2023-05-25T17:49:54","author":"Todd Baginski","authorSlug":"todd","categories":[{"id":103,"name":"Cloud","slug":"cloud","count":68},{"id":120,"name":"Flow","slug":"flow","count":18},{"id":104,"name":"Office 365","slug":"office-365","count":80},{"id":121,"name":"PowerApps","slug":"powerapps","count":57}],"tags":[{"id":42,"name":"Cloud","slug":"cloud","count":46},{"id":10,"name":"Custom Development","slug":"custom-development","count":87},{"id":5,"name":"Helpful Code","slug":"helpful-code","count":70},{"id":122,"name":"HOW TO: PowerApps","slug":"how-to-powerapps","count":38},{"id":54,"name":"Mobile","slug":"mobile","count":66}],"featuredImage":"/blog/uploads/2019/08/succulent-garden.jpg","status":"publish"},{"id":2125,"slug":"what-is-the-catalog-for-power-platform","title":"What is the Catalog for Power Platform?","content":"\n

In this video you will learn the basics about the Catalog for Power Platform and how the Catalog for Power Platform accelerates development and promotes consistency by making it easy for makers to discover and reuse Power Platform components.

\n\n\n\n

After you watch this video, check out these other great videos about the Catalog for Power Platform and related concepts.

\n\n\n\n

Accelerate development with the Catalog for Power Platform

\n\n\n\n

Sharing PCF Components with the Catalog in Power Platform

\n\n\n\n

Power Platform ALM - Choose the Right Approach

\n\n\n\n

\n","excerpt":"

Learn the basics about the Catalog for Power Platform and how the Catalog for Power Platform accelerates development.

","date":"2023-05-25T13:30:00","modified":"2023-05-25T17:52:48","author":"Todd Baginski","authorSlug":"todd","categories":[{"id":103,"name":"Cloud","slug":"cloud","count":68},{"id":120,"name":"Flow","slug":"flow","count":18},{"id":104,"name":"Office 365","slug":"office-365","count":80},{"id":121,"name":"PowerApps","slug":"powerapps","count":57}],"tags":[{"id":42,"name":"Cloud","slug":"cloud","count":46},{"id":10,"name":"Custom Development","slug":"custom-development","count":87},{"id":5,"name":"Helpful Code","slug":"helpful-code","count":70},{"id":122,"name":"HOW TO: PowerApps","slug":"how-to-powerapps","count":38},{"id":54,"name":"Mobile","slug":"mobile","count":66},{"id":112,"name":"PowerApps","slug":"powerapps","count":56}],"featuredImage":"/blog/uploads/2018/01/Ducks-Little-Miami.jpg","status":"publish"}]}},"actionData":null,"errors":null}

The Business Context

The Solution

Create the flat file data source

Create the Project

Project Inventory

Defining the Entity

Defining the Entity Service Class

BDC Explorer

BDC Model Designer

Defining the BDC Model

Quick Cleanup

Deploy and Test

Deploy

Test

Where’s the XML?

Stay Tuned!

Parts

Instructions

Tag.NET Assembly Connector

HOW TO: Create a Searchable SharePoint 2010 BDC .NET Assembly Connector Which Reads From A Flat File