Archive for the ‘Sharepoint 2010’ Category

Customizing the SharePoint forms using Infopath is easy in SharePoint 2010. You have a “Customize Form” option under List Tools -> Lists in the ribbon when you are in the list view. Below screenshot shows that option (highlighted in red).


On selecting this option, the form(Edit) is opened in Infopath Designer. Here you will be doing the changes in one infopath form(Edit) but, once you publish the form, the changes will be reflecting in all the three forms (New/Display/Edit).

So what if you want to edit three different forms in three different ways? Say New form should have all columns displayed, edit form should have some fields disabled where user cannot modify the values and display form having a different layout altogether.

Infopath solves this purpose by providing Views. We will be creating 3 views for each of the forms (New/Edit/Display). Follow the below steps to create separate views for each form.

  1. In the InfoPath designer, where your form is opened, , click on Page Design tab on the ribbon.
  2. You would be able to see the list of views available as a drop-down and also an option to create New View. You will be already having a view named Edit item (default) displayed in the drop-down.6581
  3. Already having a view for Edit form, we have to create 2 new views for New & Display. Click on New View.
  4. In the pop up opened type the name of the view(say Display Item) and click OK.
  5. Now you have an empty view, where you can add fields(from right side pane displaying fields from datasources), modify the layouts, adding rules, hiding columns. The changes you do in this view is going to affect only this view. If you want to replicate the views, just select all & copy the contents from one view & paste it in your new view.
  6. You can create another view (New Item) following the steps 3-5.
  7. Once you have created the views and done with your changes, publish the form.
  8. Now having 3 views for 3 different forms, you need to make your SharePoint list aware that which form to use which view.
  9. Open the list in SharePoint Designer, in the lists detail page, under Forms section, generally you will see DispForm.aspx, NewForm.aspx, EditForm.aspx. In addition to that since you have edited this list in infopath you will see 3 more forms namely displayifs.aspx, newifs.aspx & editifs.aspx.
  10. You need to set your views for each of this form. For each of the forms do the following steps.
  11. Open the form, select the form(highlighted in below snapshot), right click and select properties.6582
  12. In the properties window opened, under Misc header, set the DefaultView value to the view name you have created.
  13. You will be setting the values as below
    Form Name Default View Name
    displayifs.aspx Display Item
    editifs.aspx Edit item
    newifs.aspx New Item
  14. Now browse the list in IE to see different views set for different forms.

In SharePoint 2010, you create a site page which goes under the SitePages pages library (http://<siteName>/SitePages/). You edit the page and add a filter web part. The filter appears to be added successfully, but you cannot see the newly added filter on the page. You can go on adding any number of webparts. Everything will be added successfully, but doesn’t show up in the page.

You can check the same by adding  the query string ?contents=1 at the page url. You will be able to see the list of webparts in the page where you can see your filter webparts too.

You will not get this issue if you add webparts in a webpart page.

Reason:  The problem occurs because the WebPartManager.DisplayMode property is not getting set when the page is edited. The web parts expect to check WebPartManager.DisplayMode.AllowPageDesign, but for these pages it is set to BrowseDisplayMode even when editing.

Solution: To see the filter web part you’ll need to select “Edit Web Part” for any of the existing web parts you already have on the page. You can then see the newly added filter web parts you have added to the page and also configure them.

In SharePoint 2010 publishing site,  when you go to Site Settings -> Manage Content and Structure menu, you will get an error message saying One or more field types are not installed properly. Go to List settings page to delete these fields with an associated correlation ID.

This seems to be an issue created when you migrate your SharePoint 2007 site to SharePoint 2010. All the sub-sites of the current site will also have the same issue.

Reasons for the Issue :

  • The publishing site uses SharePoint Server Publishing Infrastructure to support the publishing features in SharePoint.
  • This feature automatically creates an internal List “Relationships List” which is used to store the variations details.
  • This list is normally not visible in View All Site Content menu but you can browse it through the url http://site_url/Relationships%20List/allitems.aspx.
  • The actual issue is after migration of the site, the list will have a column GroupId which is of type Text. But actually it should be GroupGuid with type as GUID.
  • So we need to resolve this column name & type inconsistency.

Solution for the Issue :

  • You will not be able to delete and re-create the column since SharePoint doesn’t support creation of column of type GUID through UI.
  • So only way is to delete and re-create the list.
  • Go to Site Settings -> Modify All Site Settings -> Site Collection Features and deactivate SharePoint Server Publishing Infrastructure feature.
  • This removes the association between the feature and the Relationships list, which allows you to delete the list.
  • Navigate to the URL http://site_url/Relationships%20List/allitems.aspx and delete the list from the list settings.
  • Now go to site collection features and activate the SharePoint Server Publishing Infrastructure feature.
  • Note that Relationships list will be created automatically. You can check the same by navigating to the URL as states above.
  • You can check the list containing the column GroupGuid of type GUID.

Now check your Manage Content and Structure page which will be working fine. Hope it helps 🙂

In SharePoint 2010, you may try deploying or upgrading a solution using stsadm and end up with the below error.

A deployment or retraction is already under way for the solution “Solution Name”, and only one deployment or retraction at a time is supported.

This issue occurs if a SharePoint solution deployment fails, yet the timer job is created and not running, you will be unable to redeploy or retract the solution.

To resolve this error and redeploy the solution, follow the below steps.

  1. Go to Central Admin -> System Settings -> Manage Farm Solutions.
  2. Cancel the deployment for your solution. It may have the status failed or deploying, which means deployment is not successful.
  3. Now redeploy your solution.

Hope this helps .

Most often, we required moving or copying a workflow that is created using SharePoint designer between sites or site collections. This was straight forward in SharePoint Designer 2007. You just need to copy the content of the workflow’s config(workflow.xoml.wfconfig.xml) file and the rules file & replaced the list GUID’s. But in SharePoint Designer 2010, there is a little tweak associated with it.

There was an option in SharePoint Designer, Export to Visio which exports your workflow as a .vwi file, and can be imported in to another site using the option Import from Visio.  But when you try that option, you will get the below message.

This workflow cannot be imported because it was created in SharePoint Designer for a different site, or the original workflow has been moved or deleted. To move a workflow between sites, use Save as Template (.wsp file) instead of a Visio workflow drawing.

So, to achieve the same follow the steps below.

  1.  In the first(source) site, create the required workflow and publish it.
  2. Now select Export to Visio option which allows you to save the workflow with a .vwi extension. (Refer this workflow hereafter as source workflow).
  3. Now go to the destination site where you want the workflow to be copied, and create a new workflow with the same name as the previous one & publish it.
  4. Now select Export to Visio option which allows you to save the workflow with a .vwi extension. (Refer this workflow hereafter as Destination workflow).
  5. Now you will be having two .vwi files (one of source workflow’s – SourceWorkflowName.vwi  and other of the destination workflow’s – DestinationWorkflowName.vwi). Now add .zip extension to both the files. Now your files names should be &
  6. Now open both the zip files, copy workflow.xoml.wfconfig.xml from destination workflow to source workflow. (Its destination to source and not source to destination).
  7. From now on, we will not use the file  So ignore that file.
  8. Remove the .zip extension from which gives you the   SourceWorkflowName.vwi file.
  9. Now, go to the destination site, open workflows and click Import from Visio and browse to the SourceWorkflowName.vwi file.
  10. That’s it and your workflow is copied. You can publish the workflow and run it.

PS : In case if your list’s GUID’s (for those lists that you have used in workflow – tasks list, history list or any other lists used in workflow steps) have been changed from source & destination site, you may need to update those steps in the workflow.

Hope this helps.