Wednesday, 22 January 2014

SharePoint - Field type [FieldName] is not installed properly. Go to the list settings page to delete this field.

Sorry, something went wrong
Field type [FieldName]  is not installed properly. Go to the list settings page to delete this field.  

This is caused when a FieldType has been created usually via a custom solution (WSP), and has been used somewhere, then uninstalled while still being used somewhere on the Site Collection.  This error message is similar on all versions of SharePoint 2007/2010/2013.

Usually you will have one or more Site Columns that are using the FieldType, and possibly one or more Content Types that are using that Site Column, and then most likely one or more Lists/Librarires using the Site Columns or Site Content Types.

If you want to remove the Field Type Completely, steps to resolve are as follows:

  • Try to delete the Site Column or Content Type from every list it is being used on.  If you can't delete the Content Type from the list, you will have to delete the list.
  • Delete the Content Types using the Site Column (Site Actions > Site Settings > Site Content Types)
  • Delete the Site Column (Site Actions > Site Settings > Site Columns)
I was able to get up to the last point but still couldn't delete the Site Column as it was causing an error just trying to navigate to it.  In that case, the following Powershell script can be ran to remove the Site column.

$site = Get-SPWeb http://rootweb
$column = $site.Fields["Field Type Title"]
$site.Fields.Delete($column)




Powershell grabbed and modified from here, Thanks! http://www.sharepointfix.com/2011/04/powershell-script-to-delete-site.html 

SharePoint 2010 - Access List / Library Data Across Web Applications

We can do this using jQuery.js and SPServices.js
Only issue is that you will most likely be forced to receive a notification every time the page loads:

"this page is accessing information that is not under its control"

I found that although it's possible the solution was not ideal, but have not yet found an alternative.  However I thought I would provide it in case anyone else has a need for it.

The code below will retrieve the list item information from the Page library at http://intranet.  CAML query retrieves the most recent 4 articles from the Page library and the last line appends the HTML statement to the page.

The HTML statement that is created grabs the value of the FileRef Field and places it inside a div.

----------------------------------------------

$(document).ready(function() {
  $().SPServices({
    operation: "GetListItems",
    async: false,
    webURL: "http://intranet",
    listName: "Pages",
    CAMLViewFields: "<ViewFields><FieldRef Name='Title' /><FieldRef Name='ArticleStartDate' /><FieldRef Name='PublishingRollupImage' /><FieldRef Name='FileRef' /></ViewFields>",
    CAMLQuery: "<Query><OrderBy><FieldRef Name='ArticleStartDate' Ascending='FALSE' /></OrderBy></Query>",
    CAMLRowLimit: 4,
    completefunc: function (xData, Status) {
      $(xData.responseXML).find("[nodeName=z:row]").each(function() {
        var liHtml = "<div id='div>" + $(this).attr("ows_FileRef") + "</div>";
        $("#tasksUL").append(liHtml);
      });
    }
  });




Friday, 17 January 2014

SharePoint 2013 - Cannot open excel or word documents

Have you recently upgraded to SharePoint 2013 but can't seem to open excel or word docs inside a Document Library?

Are you getting a URL that starts something like this?

  • ms-word:nft|u| 
  • ms-excel:ofv|u|

Chances are it's because you have both Office 2010 installed on your computer as well as either the full Office 2013 suite or any single Office 2013 product (Here's looking at you SharePoint Designer 2013!!!).

The reason for this is related to the new Microsoft SharePoint Foundation Support feature that gets updated when you install an Office 2013 product, in turn updating a few pointers to look at the Office15 Hive folder.

Others have solved this issue before me, but to save you having to read lots of comments, the solution is to install Office 2010 SP2.

Here's some links to a few blogs that helped me realise the cause and find the solution.