So . . . here I am playing around with PowerPivot to get ready for a demo. As this is a group from the SharePoint dev team (actually SharePoint Online), I wanted to include some cool SharePoint functionality [...]]]> Updated 28-Oct-2010: Some folks are reporting that an iisreset is needed to make the updates visible to SharePoint.

So . . . here I am playing around with PowerPivot to get ready for a demo. As this is a group from the SharePoint dev team (actually SharePoint Online), I wanted to include some cool SharePoint functionality into the demo. Trying to be cool and ‘wow’ them, I decide to use a SharePoint list as a data source. I want to show the data mashup capabilities of PowerPivot so I have the bulk of my demo come from the Contoso sample database (the three product catalog tables) and the 4 million row Sales Fact table.

I create my SP list by extracting the 11 distinct manufacturers – and I assign them to a ‘shipper’ that I made up.

When I go to SharePoint an click on:

PowerPivot comes up but it returns an error:

"For security reasons DTD is prohibited in this XML document. To enable DTD processing set the ProhibitDtd property on XmlReaderSettings to false and pass the settings into XmlReader.Create method."

So it turns out that I forgot (it happens to the best of us) to install the ADO.NET Data Services 3.5 SP1, located here: http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=3e102d74-37bf-4c1e-9da6-5175644fe22d

Which I would have known if I had taken my own advice and read BOL beforehand. Read the “New server” installation notes here: http://msdn.microsoft.com/en-us/library/ee210708.aspx#nextsteps

So the moral of the story is: RTFM

After installing ADO.NET Data Services on my SharePoint site, I was able to bring up the data feed in PowerPivot – setup the relationship between the Manufacturer field in the SharePoint list and the Manufacturer field in the Contoso database and I was off and running . . . I also setup daily data refresh job . . . and I could see the Gallery snapshot changing as I entered new data into the SharePoint list . . WOW!

Enjoy!

Enjoy!

_-_-_ Dave

First via [...]]]> As more and more folks start to get into PowerPivot and SharePoint, there is a need to programmatically write entries into the ULS. Since all of PowerPivot and all of SharePoint share this common logging infrastructure, why not also include log entries from your own processes. Here is some sample code for doing that:

First via PowerShell:

$diagSvc = [Microsoft.SharePoint.Administration.SPDiagnosticsServices]::Local
$category = new-object Microsoft.SharePoint.Administration.SPDiagnosticsCategory(“My Category”, 
                                 [Microsoft.SharePoint.Administration.TraceSeverity]::Monitorable, 
                                 [Microsoft.SharePoint.Administration.EventSeverity]::Error )
$diagSvc.WriteTrace(0, $category, [Microsoft.SharePoint.Administration.TraceSeverity]::Monitorable, “Write your log here” )

Now via C#:

using System;
using System.Collections.Generic;
using System.Linq;
using System.Text;
using Microsoft.SharePoint.Administration;
namespace WriteIntoULSLog
{ 
    public class Program 
    { 
        public static void Main(string[] args) 
        {
            SPDiagnosticsService diagSvc = SPDiagnosticsService.Local; 
            diagSvc.WriteTrace( 0, 
                new SPDiagnosticsCategory(“My category”,  TraceSeverity.Monitorable, EventSeverity.Error),
                    TraceSeverity.Monitorable,
                    “Writing to the ULS log:  {0}”,
                    new object[] { “SharePoint 2010 rocks!”});
        } 
    }
}

Enjoy.