Skip to main content

How to deloy InfoPath 2010 "Administrator-approved form template" to SharePoint 2010 programaticaly


Scenario: you've developed and InfoPath 2010 form. This form contains code that requires full trust, so you need to deploy it as a administrator-approved form template.

This requires an farm administrator to check, upload and activate the form for the site collection.

Solution: to automate this operation I created a farm level feature - when the feature is activated upload the form programmatically and when the feature is deactivated remove the form programmatically.

Here is how I did it:

1. Create an Empty SharePoint Project and set it to be deployed as a farm solution

2. Add an Empty element item - EmptyElement1. This will also generate a feature - Feature1

3. Delete the Elements.xml file of the EmptyElement1

4. Copy/Paste the InfoPath 2010 form into the EmptyElement1

5. Right click on the added form and click Properties:
 - Deployment Type: ElementFile
 - Deployment Location> Path: set it to blank

6. Open the generated feature, Feature1

7. Set the scope to Farm level and save it

8. Right click on the feature and select "Add Event Receiver"

9. Comment out the FeatureActivated and FeatureDeactivating methods

10. Add the following code to the FeatureActivated method to upload the form:

  SPSecurity.RunWithElevatedPrivileges(() =>
  {
   SPFarm localFarm = SPFarm.Local;
   FormsService localFormsService;
   string solutionPath = properties.Definition.RootDirectory + @"\Form.xsn";
   try
   {
    localFormsService = localFarm.Services.GetValue(FormsService.ServiceName);
    localFormsService.FormTemplates.UploadFormTemplate(solutionPath);
   }
   catch (Exception ex) {
    // Handle exception Here
   }
  });

10. Add the following code to the FeatureDeactivating method to remove the form:

  SPSecurity.RunWithElevatedPrivileges(() =>
  {
   SPFarm localFarm = SPFarm.Local;
   FormsService localFormsService;
   string solutionPath = properties.Definition.RootDirectory + @"\Form.xsn";
   try
   {
    localFormsService = localFarm.Services.GetValue(FormsService.ServiceName);
    FormTemplate formTemplateToRemove = (from formTemplates in localFormsService.FormTemplates
              where formTemplates.DisplayName == "Form"
              select formTemplates).Single();
    localFormsService.FormTemplates.RemoveFormTemplate(formTemplateToRemove);
   }
   catch (Exception ex) {
    // Handle exception Here
   }
  });

11. Build and deploy the solution.


That is it!


Note that you need to reference the Microsoft.Office.InfoPath.Server.dll. This is usually located here:  C:\Program Files\Microsoft Office Servers\14.0\Bin\
Labels:

Comments

Post a Comment

Popular posts from this blog

How to create a custom Workflow Task / SharePoint Server Workflow Task content type using Visual Studio?

If you are designing an Workflow and you want to create custom  Workflow Task or SharePoint Server Workflow Task  using Visual Studio interface then you'll need to make these two content types visible. To make them visible I'm using the following  PowerShell   script: $site = Get - SPSite "http://site/url/here" $web = $site . RootWeb # Workflow Task $contentType = $web . ContentTypes [ "Workflow Task" ] $contentType . Group = "Custom Content Types" $contentType . Hidden = $FALSE $contentType . Update () # SharePoint Server Workflow Task $contentType = $web . ContentTypes [ "SharePoint Server Workflow Task" ] $contentType . Group = "Custom Content Types" $contentType . Hidden = $FALSE $contentType . Update () $site . Dispose () Then when you can add a new Content Type from Visual Studio and you will see the two Content Type in the list. To revert these changes run this PowerShell script: ...
Post a Comment
Read more

PowerShell script to add work email to the list fields for the author

The Author (Created By) field is actually an lookup field to the hidden User Information list. If you need to add the work email of the Author (Created By field) user to a specific list it can be done by adding a dependent lookup field for the Author field: $site = get - spsite "site url here"; $list = $site . RootWeb . Lists [ "list name" ]; $createdByEmailGuid = $web . Fields . AddDependentLookup ( "Work e-mail" , [ Microsoft . SharePoint . SPBuiltInFieldId ]:: Author ); $createdByEmail = $web . Fields . GetFieldByInternalName ( $createdByEmailGuid ); $createdByEmail . Description = "Work e-mail address of the Author."; $createdByEmail . LookupField = $web . Fields [[ Microsoft . SharePoint . SPBuiltInFieldId ]:: EMail ]. InternalName ; $createdByEmail . Update (); $web . Update (); $list . Fields . Add ( $createdByEmail ); $list . Update (); If additional fields are needed the same method can be applied. Here is a li...
Post a Comment
Read more

SharePoint Designer 2010 Reusable Workflows with Lookup Values

When you create a Reusable Workflow in SharePoint Designer 2010, that uses lookup values, and you try to deploy it in another environment, the lookup values will get broken. This is happening because the list you are reading the lookup values from has another Guid. Here is what I came up with to make this deployment easier: Deploy the reusable workflow in the new environment. Open the site you have deployed the workflow solution in SharePoint Designer Go to the related list (List and Libraries > Your Related List Name) and copy the new List ID value. Go to All Files > Workflows >   Your Workflow Name >  Your Workflow Name. xoml and open it in SharePoint Designer as XML ( right click on it > Open with >  SharePoint Designer (Open as XML) ) Find an  and you will find the old list guid in the ListId  attribute  Replace the old guid value with the new one Save it and close the window. The workflow should be pointi...
Post a Comment
Read more