Skip Ribbon Commands
Skip to main content



Quick Launch

Just a place for me to store SharePoint related information.
February 19
Report not viewable by members of "Viewers" group

The report will not be explicitly published after deploying to the library.  I added the version column to the view to ensure that the version of the report is explictly *.0.

January 29
Enabling SSRS to work with Access Services Reports

Web Link:

Microsoft Link:​

November 19
Managing Field Names in Form Library for InfoPath 2007 Data Columns
November 15
Associating an Event Receiver with a specific Form Library

Not sure why this is an issue, but of course it is.  I'm trying to associate an Event Receiver with a specific Form Library in Visual Studio and it won't let me.  It will let me associate it to every List in the site, but not my Form Library.  I can associate it to the List Type Form Library (Code 115).

Here's the fix:

November 13
Disable InfoPath 2010 Validation Errors on Submit


So, I am building a form that will write line items to a Task List.  The form has multiple tabs and has a number of required fields.  These required fields should be filled out prior to formal submission of the form.  However, I need to be able to submit data back to SharePoint for these tasks regardless of the validation.


I found a great article here:


public void SaveAsDraftButton_Clicked(object sender, ClickedEventArgs e)

I had to make some changes to this for it to work in my scenario.  I had to backup the errors prior to deleting them because they were valid. 

So I had to do this:


     public List<BackupFormError> BackupErrors(FormErrorCollection Errors)
         List<BackupFormError> backupErrors = new List<BackupFormError>();


         foreach (FormError formError in Errors)
             BackupFormError backupError = new BackupFormError();
             backupError.Context = formError.Site;
             backupError.Name = formError.Name == String.Empty ? formError.Site.LocalName : formError.Name;
             backupError.Message = formError.Message;


         return backupErrors;


The Errors collection on the form is a static reference (I believe).  The FormErrorsCollection is also an abstract type meaning I couldn't create a variable to hold the errors as a backup and then write them back.  Instead, I created a basic inline object and added those objects to a Generic List.

It worked very well, with the exception that the .Name property of the Error was always blank.  When creating a new FormError, it would throw an exception when the object was created with a blank .Name property.

August 03
SharePoint Feature not automatically activated upon deploy


I completed development on my latest webpart for approval of list items (post approval to be submitted to a database).  I am leveraging the Visual WebPart for this solution.  I noticed that after the default WSP deployment, the ASCX file was not deployed.  Additionally, I could not find the Feature in either the Site Collection solutions or Farm Solutions in Central Admin. 


Turns out that for some reason, the default is to deploy but not to activate the Feature.  The issue is that the web part files are not deployed and the .webpart file is not loaded into the gallery.  This causes a "where is it?" panic thinking that something is wrong with the deployment.


If you go into the SharePoint root folder and traverse to the Features Folder, you should be able to locate your feature that was deployed.  The Name of the Feature is the name of the folder.  You can then run the ​Enable-SPFeature powershell command to activate the feature.  Once activated, the necessary files will be copied and installed.



May 14
SharePoint Web Services Round Robin Service Load Balancer Event: Initialization
April 27
8 Core Beliefs of an Extraordinary Boss
April 27
What is the value of a SharePoint Rockstar in your environment?
April 27
What to expect in SharePoint 15
1 - 10Next

 About this blog


About this blog

Welcome to my SharePoint Blog.  I have been working with Microsoft SharePoint for about 5 years now. 

This page is a way for me to record items relating to SharePoint and elaborate on the daily musings of my work.