Thursday, February 18, 2010

How to: Upload a file/document using the SharePoint Object Model

With this simple article, I'm walking you through the process of uploading any file to your Document Library.

Note; Since this is done through the local API, you need to have this code running on the server. That means that it's ideal to use in for example a FeatureReceiver or EventReceiver. You cannot run this code on the client in e.g. a Windows Form, then you'll need to utilize the SharePoint WebServices instead.

Code to upload a file/document to a SharePoint Document Library

Use the following code to get you started in uploading a file using the object model. It really isn't that hard :-)

// Getting a reference to the document library
var sp = new SPSite("http://localhost");
var site = sp.OpenWeb();
var folder = site.GetFolder("Documents");
var files = folder.Files;

// Opening a filestream
var fStream = File.OpenRead("C:\\MyDocument.docx");
var contents = new byte[fStream.Length];
fStream.Read(contents, 0, (int)fStream.Length);
fStream.Close();

// Adding any metadata needed
var documentMetadata = new Hashtable {{"Comments", "Hello World"}};

// Adding the file to the SPFileCollection
var currentFile =
files.Add("Documents/MyDocument.docx", contents, documentMetadata, true);

site.Dispose();
sp.Dispose();

As you can see in the image below, the metadata "Comments" has been filled in as per the metadata I specified in the code above.

File uploaded using the Object Model

Simple as that. Over and out!

Getting Started with the Business Data Catalog

In this article I will guide you through the very basics of getting started with Business Data Catalog, BDC:

  1. Install the AdventureWorks 2008 Sample Databases
    1. We will use this database as our example for retrieving data using the BDC.
  2. I will step you through the simple process of creating your ADF (Application Definition File)
    1. We will use this file as our import connection
  3. I will guide you through how we can import this ADF file and create our BDC Application
  4. Lastly, I will guide you through the process of creating a basic site and use some of the basic BDC Web Parts

Install the AdventureWorks sample database

  • You'll need to go and download the AdventureWorks sample databases
    image

  • Just finish the installation by clicking next a couple of times and let the installer do it's normal Microsoft-installer magic.
  • You should now see a couple of new databases in your SQL Server Management Studio:
    image
    AdventureWorks, AdventureWorks2008, AdventureWorksDW, AdventureWorksDW2008, AdventureWorksLT, AdventureWorksLT2008

Alright - We've got our databases, now we need to start thinking about how we will get data from our SQL server into SharePoint. This is done by creating/generating an Application Definition File (ADF) as you will see in the next section.

Creating the ADF (Application Definition File)

Alright, there's a few different options to create your ADF (Application Definition File). I will show you how to get started with using the free tool called "Application Definition Editor" that comes with the latest SharePoint Server SDK.

Note: See the bottom section in this article for a summary of links to all resources mentioned in the article.

After you have installed the latest SDK, you can choose to install the "Microsoft BDCTool" located here by default: "C:\Program Files\2007 Office System Developer Resources\Tools\BDC Definition Editor". Which will give you the following item in your Start Menu:
image

Launch the BDC Application Definition Designer

Click the application and launch the editor. You will see an interface like this:
image

Create or import your ADF file

There's basically two alternatives when it comes to editing an ADF (Application Definition File).
One is to create a new one (which I will guide you through first), and the other is to import an existing one (which I will show you after the first alternative).

Alt 1) Creating our own ADF file
Now we're going to connect to our newly created sample-databases and create an ADF file for use with those databases.
  • Click on ADD LOB System
  • Choose Connect To Database
  • You will see a nice popup-dialog where you will be able to enter the connection details to your desired database
    • Enter your connection details, example:
      image
  • You are presented with the "Designer Surface" that looks something like this:
    image
  • In our case, we're going to use the table called "vEmployee" which exist in the AdventureWorks database in order to pull out some information about our employees.
    • Search for the table called vEmployee and drag it out to the Design Surface
    • Search for the table called vEmployeeDepartments and drag it out to the Design Surface
    • It should look something like this:
      image
    • Make any necessary changes, then click OK
    • You'll see a view similar to this one after some tweaking:
      image
    • After you've done the necessary changes to your configuration, making sure it's a valid ADF with proper filters, enumerators and methods or whatever you need in your application then smile, because we're done with that part!
Alt 2) Importing an existing ADF file

If you don't want to do everything from scratch or you've already got an ADF file that you wish to modify, you can do so by importing an existing ADF file into the Definition Editor. Here's how:

  • Open the BDC Definition Editor tool, then click the "Import" button in the menu:
    image
  • Browse to your existing ADF file and choose to import it. Simple as that.
    (I am importing a file called BDCAWDW.xml, which contains definitions for Product, Reseller, ProductSubcategory, ProductCategory as shown below)
  • You'll see the imported ADF file's structure immediately in the designer, under the prerequisite that your SQL connection string in the ADF file is valid:
    image

Note: I will not detail how you create filters, finders, methods etc. in this article. You can read more about that here:
http://msdn.microsoft.com/en-us/library/ms145931(SQL.90).aspx

I may cover the topic of ADF-functionality in another article later on.

Generate the ADF file from the designer

I really don't need to tell you this, but there's a button called "Export" which you use to export the definition you've created using the definition editor to an xml file:
image

Import the ADF file

If we have gotten this far, we might as well get the last few bits in place.
What we now need to do is to import our ADF file into SharePoint, since that's where it should reside. Follow along with these few simple steps to make sure you're properly importing your file into SharePoint.

  • Navigate to your Shared Services Provider Administration site (You can access your SSP through Central Administration)
  • You are presented with a section called "Business Data Catalog" where you'll find a bunch of different alternatives.
  • Make sure you have the permissions to modify the BDC (See the link Business Data Catalog permissions)
  • Click "Import application definition"
    image
  • Browse for your .xml file and click "OK":
    image
  • You'll see a progress bar (You don't see that a lot in SharePoint. I love it!), telling your how the import process is going:
    image
  • When it's done, you'll click "OK" and be presented with an overview of your imported BDC Application:
    image
Configure permissions on the BDC Application Definition

In order for all users to be able to select/read data from your BDC Application, you'll need to make sure they've got the appropriate permissions to actually do so.

Usually I do this setting on each of the imported entities, in case you want specific permissions on different entities - instead of on the entire application.

  • Select the DropDown list on your first entity and choose "Manage Permissions":
    image
  • Choose "Add Users/Group":
    image
  • Enter "NT AUTHORITY\AUTHENTICATED USERS" and choose "Select in Clients":
    image
  • Repeat these steps for the other entity as well.
  • You're done.

Now we have created or imported an ADF file with the Business Data Catalog Definition Editor tool, exported it to an .xml file, imported it into SharePoint, set basic permissions on the entities.

Next, we should make sure that the application works in SharePoint by adding a Business Data Catalog-WebPart to a page.

Use the basic built-in BDC Web Parts

Awesome. Now that we have gotten this far by importing an ADF file into SharePoint and set appropriate permissions on the entities - We're ready to actually use the ADF connection to view stuff in our database.

Note: I have created a new blank site where I can easily show the built-in BDC Web Parts - so that's where I am adding my Web Parts.

  • Add two Web Parts to your page called "Business Data List" and "Business Data Item":
    (Note that when you've configured a BDC application, you'll see the Business Data web parts)
    image
  • Choose to edit the properties of the Business Data List Web Part:
    image
  • Click the Browse-icon to the right to pop up the BDC entity chooser:
    image
  • It will present you with the following interface (note, BDC applications will of course vary depending on what you have imported..):
    image
  • Double click the "Employee" type, and then click "OK" in your Web Part property window.
  • Repeat this process for the "Business Data Item" Web Part, and select "Employee" in the BDC Type Picker as well.

Now we've got one BDC List Web Part which will list all employees, and one BDC Item Web Part that will display details about the employee we select.

In order for this to work we must connect the two Web Parts.

  • Edit menu of your Web Part -> Connections -> Send Selected item To -> Employee
    image

Test our BDC Application out, and make sure it works!

  • Choose "LastName" then "contains" and enter "smith":
    image
  • Select one of the results by clicking the radiobutton to the left, and see that the result (details) about the Employee shows up in the connected Web Part:
    image

Resources and links

Summary

This article is a basic step-by-step guide to getting started with BDC in MOSS 2007. I've shown you every step from creating the databases required (in our case some sample databases) to creating the ADF file and to finally utilize the BDC connection from a site, using the BDC Web Parts.

Monday, February 1, 2010

SharePoint 2010 New Features

Microsoft has released a couple of sneak peek videos about SharePoint 2010 at http://www.microsoft.com/sharepoint

Here are some of my notes from these videos

Business Value

The SharePoint pie from MOSS 2007 has been changed for 2010. Instead of focusing on generic portal topics, the focus is more on the business value of SharePoint. Here is the new pie

New%202010%20Pie

Sites

Sites are all about sharing info with employees/partners/customers – empowering customers across all mediums
Team Sites, Internet Facing sites, extranets for customers and partners

Communities

Ad-Hoc Communities
Communities in terms of hierarchy (comes from AD)
Communities now include Business Partners. You could search for users who are non-employees

Content

Collaboration Content
Line of Business Content
People Centric Content

Search

FAST Search is integrated into SharePoint
Highly scalable Search engine
Emphasis on getting the right results on the first page
Enhanced People Search
Enhanced Business Data Search

Insights

Combination of all the above
Microsoft’s vision is a decision engine that brings other tools into unison

Composites

Help rapidly create dynamic business solutions
End user applications
Business Processes
Tools and integration with SharePoint Designer, Visual Studio

New Features

  1. Ribbon inside SharePoint
  2. Customizable Ribbon
  3. Contextual
  4. Removable and users have the option to go back to the MOSS 2007 interface
  5. Asynchronous user interface – minimal postbacks
  6. Dialogs employ DHTML effects to gray the background and provide user dialogs

Functionality previously available under the Content and Structure pages are now available in the main library

Multi select documents to checkout /check -in/delete etc.


Customization Capabilities

  1. Page edits are called Web-Edits – This replaces the Site Text and font etc.
  2. Live Preview of fonts/colors etc, similar to Office 2007
  3. Upload and modify Images directly instead of uploading first to a image library
  4. Picture Tools provide Resizing of pictures directly using the picture
  5. Changing styles like having borders etc. for images

SilverLight

  1. Add SilverLight web parts without additional configuration
  2. Just point the web part to a XAP file in a document library
    Interactive zoom is available on SilverLight web parts

Theming

  1. You can theme SharePoint using the same theme as PowerPoint
  2. e.g Upload a Powerpoint theme
    Choose the theme and apply it to the site
    Now the site looks like the Powerpoint slide
    You can preview a theme on the site before applying it
  3. Firefox is fully supported and can do the same things as IE
  4. Completely redesigned Sharepoint Designer with Ribbon

Visio Services

  1. Visio can connect to backend and visualize the data
  2. Can publish visio into SharePoint and can render them without the need for visio on the client (similar to Excel Services)
  3. This functionality is called Visio Services
  4. Can zoom in and zoom out of diagrams
  5. Needs a good Visio design first for Business processes

BDC is now Business Connectivity Services

  1. Can take LOB data offline using SharePoint workspace Manager(previously Groove)
  2. Tools in SPD and VS for modeling LOB entities
  3. External data are called Entities – they live in BCS and you can work with them in SPD
  4. External Content types based on these LOB entities can be created within SPD
  5. There is a browser within SPD which can browse SQL Databases and provide views/stored procs etc.
  6. You can right click on an entity and create CRUD operations on it using a simple wizard and publish from SPD
  7. External data gets converted to a list like view
  8. Users can filter and sort BCS data and work with it like they would with a SharePoint list
  9. Users can seamlessly update data in 2010, which will automatically update the LOB system
  10. You can create a Word template with BDC elements and publish to a library. When the user creates a new document they can pick those BCS entities within Office
  11. To take items offline use Groove – SharePoint workspace manager – Click on Sync to Computer
  12. Lists/Libraries are all synced
  13. LOB data flows offline in Groove
  14. Can edit LOB data when offline and sync back when connected

Whats New for Developers

  1. Visual Studio 2010 has Visual Web part Designer. No more building tables for layout. You can drag and drop and create controls within web parts, similar to ASP.NET forms
  2. Developer Dashboard – can allow any page to provide debug info
  3. LINQ for SharePoint has been released and allows developers to use LINQ objects to query SharePoint lists
  4. Client Object Model – can run code on the client using JS/.NET. This is especially useful when building Silverlight applications
  5. Supports TFS , automated builds
  6. New Project Templates are available in Visual Studio 2010
  7. Comes with a SharePoint Server Explorer within VS
  8. Can lookup Sites/Lists etc. as just like SQL Explorer in visual studio
  9. Can automate post deployment tasks – no more post deploy batch files required, UI to specify deployment steps
  10. There is a BDC explorer within VS to explore LOB data from within VS
  11. Visual Web part project comes with Features and Packages automatically. Complete drag and drop functionality to visually build a web part
  12. SilverLight can use Client Object Model to access list data using Microsoft.SharePoint.Client namespace
  13. Runs CAML queries asynch and provides a rich client side object model to access data

Whats New for Administrators

  1. New SharePoint best practices analyzer – Comes with a set of pre-built rules , You can build your own rule if you need. It can automatically correct issues provided you set it up to do so
  2. New Central Admin Console look and feel. Items are grouped differently compared to the 2007 version
  3. New Backup and Restore Tools in the UI
  4. Visual Upgrade option – Can upgrade 2007 to 2010 and keep the old layout and customizations
  5. New SQL Logging Database – Developers can write code to log to this SQL database , Can write your own events into the logging database, Whole bunch of out of the box reports for logging
  6. Scalable List infrastructure - Can control how many items get returned from a list , Can set happy hour deadlines to filter the number of items in a list based on time of day
  7. Unattached Content DB recovery – If you need to recover sites/lists from a DB backup you can do so without restoring it onto a temporary site. You can also – Browse content, Backup the site , Export site and all of this without restoring it onto a site
  8. Upgrade looks and feels like 2007 – Can preview the new look and feel and revert back to the old version