Wednesday, 24 July 2013

How to Update the SharePoint 2013 Term Store by Importing it from an Excel 2013 Spreadsheet

Changing your Region Settings

The first thing you need to do is make sure your region setting are formatted correctly. This is because the file format used by the SharePoint Term Store is a csv. This converts table using the “List separator” in your PC’s region settings. If you don’t set these first you have difficulty opening and converting the spreadsheet to and from a csv file format.

The csv extension literally stands for Comma Separated Values.

Change the “List separator” from a semi-colon to a comma

  1. Open “Control Panel”
  2. Click “Region” or “Region and Language”, depending on your Windows operation system
  3. Click “Additional settings…”
     photo Region1.jpg
  4. Change:
    a. Decimal symbol                .               (full stop)
    b. List separator                     ,               (comma)
     photo Region2.jpg
    Both need to change. It seems to conflict if you just change the “List separator” and not both. If they are both comma’s, the csv conversion returns semi-colon’s.
  5. Click “OK”
  6. Click “OK”

Import the csv sample template from SharePoint 2013 Term Store

  1. Open SharePoint 2013
  2. Click the cog (Site Actions), top right corner
  3. Select “Site Settings”
  4. Click “Term store management”, under “Site Administration”
  5. Select the Managed Metadata Service application, on the left tree view
     photo TermStore3.jpg
  6. Click “View a sample import file”, on the right (properties pane)
     photo TermStore2.jpg
  7. Click “Save”

Working on the Terms

  1. Open this file (ImportTermSet.csv) with Excel 2013.
    If all the region setting are correct, it will open correctly, in the correctly formatted columns.
     photo TermStore4.jpg
To see the raw csv, you can open it in Notepad.
For more on the Managed metadata input file format, here: http://technet.microsoft.com/en-us/library/ee424396.aspx

When creating your Managed Metadata terms store it is always better to plan what you are going to do and what they are going to be used for. TechNet has some nice articles on this: http://technet.microsoft.com/en-us/library/ee530389(v=office.15).aspx

Compare Excel spreadsheet with Term Store

What will the spreadsheet going to look like in the Term Store?

 photo TermStore5.jpg

 photo TermStore8.jpg


Save to csv

If you have competed creating the terms in Excel and have the spreadsheet in xlsx format and you want to re-save it to into csv format.
  1. Open Excel 2013
  2. Click "File" tab, on the Ribbon
  3. Select "Save As", on the left
  4. Click "Browse"
  5. Select the file type: CSV (Comma delimited) (*.csv)
     photo TermStore9.jpg
  6. Give the file a relative name
    e.g. ImportTermSetNew

Import csv to SharePoint 2013 Term Store

Remember permission. The authentication account which you use to access the Term Store Management Tool, must be listed as a "Term Store Administrator", or you will not be able to accomplish this task.
  1. Open SharePoint 2013
  2. Click the cog (Site Actions), top right corner
  3. Select “Site Settings”
  4. Click “Term store management”, under “Site Administration”
  5. Select the Managed Metadata Service application, on the left tree view
  6. On the left, in the tree view, select the “Term Group” you would like to upload to.
  7. Select “Import Term”
    e.g.: Test Term Group
     photo TermStore6.jpg
  8. Click “Browse”
  9. Choose the relevant csv file
    e.g.: ImportTermSetNew.csv
  10. Click “OK”
     photo TermStore7.jpg

Thursday, 18 July 2013

How to update the Content Type Hub URL

We recently moved our DEV SharePoint 2013 DB’s to our QA environment. We moved the main content DB, the managed metadata DB, and the content hub DB. Everything was recreated and moved over correctly. 

But when I went to change a content type in the Site Collection Content Type Hub, the content type appeared as “read only”. After some investigation I realised the “Managed Metadata Service” was still showing the old DEV Content Type Hub URL.

How to check the Content Type Hub URL:

  1. Open Central Administration
  2. Click “Manage service applications”, under “Application Management”
     photo Picture1-2.jpg
  3. Select “Managed Metadata” service (the first one). Click on the side, to select it, but not open it.
  4. Click “Properties”, in the Ribbon
     photo Picture2.jpg
  5. Scroll to the bottom, and confirm the Content Type Hub is the correct Content Type Hub URL

How to update the Content Type Hub URL:

  1. Goto the server (Server 2012) which hosts the SharePoint 2013 Central Administration.
  2. Open the “SharePoint 2013 Management Shell” as the Administrator
    a.  Open the Search
         i.  Hover over the bottom right corner
         ii. Click on the Search icon
    b.  Search for “SharePoint 2013 Management Shell”
    c.  Right click “SharePoint 2013 Management Shell”
    d.  Select “Run as Administrator”, at the bottom
  3. Run the script below:
    Set-SPMetadataServiceApplication -Identity "{Managed Metadata Service name}" -HubURI "{Content Type Hub URL}"
    Example:
    Set-SPMetadataServiceApplication -Identity "Managed Metadata" -HubURI "http://vm-sharepoint2013-qa-hub"
  4. Check the Content Type Hub URL is correct, see above section (How to check the Content Type Hub URL)

Now to edit the content type:

  1. Open the Content Type Hub (http://vm-sharepoint2013-qa-hub)
  2. Click the cog (Site Actions), top right corner
  3. Select “Site Settings”
  4. Click “Site content types”, under “Web Designer Galleries”
  5. Click on the Content Type you want to change
  6. Click “Advanced Settings”, under "Settings", near the top
     photo Picture3.jpg
  7. Select “No”, under “Read Only”
     photo Picture4.jpg
  8. Click “OK”
  9. Now change the Content Type as needed.

Friday, 5 July 2013

How to find a particular Site Collection URL from SharePoint Central Administration

  1. Open “Central Administration”
  2. Click “Manage web applications”, under “Application Management”
     photo Picture1-1.jpg
  3. Here you will see the list of all the Site Collection in your farm

Friday, 28 June 2013

Deploying a WSP to SharePoint 2013

How to deploy a WSP to SharePoint Farm Solution library

This need to be done on the Server which host the SharePoint Central Administration.
  1. Add the WSP to the SharePoint Server
    1. The first thing you need to do is copy over the wsp deployment file. The best things to do is to create a deployment folder, where all the deployed files are kept.
    2. Copy over the deployment files to: c:\Deploy\WSP
  2. Add the WSP to the SharePoint Farm Solution library
    1. Open “SharePoint 2013 Management Shell “ as administrator
      a. Open the Search on Server 2012
      b. Search for “SharePoint 2013 Management Shell”
      c. Right click “SharePoint 2013 Management Shell”
      d. Select “Run as Administrator”
    2. Run this script: 
      Add-SPSolution "c:\Deploy\WSP\{file name}.wsp"  
  3. Deploy the WSP to the SharePoint Farm Solution library
    1. Open Central Administration
    2. Click “System Settings”
       photo Picture1.jpg
    3. Click “Manage farm solutions”, under “Farm Management”
       photo Picture103.jpg
    4. Click on the {file name}.wsp package
    5. Click “Deploy Solution”
       photo Picture106-1.jpg
    6. Deployment settings
      Deploy When: Now
      Deploy to: All content Web application
    7. Click “OK”

How to activate the WSP Feature on the Site Collection

  1. Activate the WSP Feature on the Site Collection
    1. Open the Root Site (the Site Collection)
    2. Click the cog, in the top right corner (Site Actions)
    3. Select “Site Settings”
    4. Click “Site collection features”, under “Site Collection Administrator”
    5. Go to {file name}
    6. Click “Activate”, to the right

Thursday, 13 June 2013

How to troubleshoot a SharePoint Designer 2013 Workflows

How does it all fit together:

  1. The workflow name
  2. The workflow task list
  3. The workflow "Stage". This is new in SharePoint Designer 2013 Workflows
  4. The workflow history log list [site name]/Lists/Workflow%20History

Workflow Status page:

SharePoint Designer 2013 Workflow Error photo SharePointDesigner2013WorkflowError1.jpg

Workflow setting in SharePoint Designer 2013:

SharePoint Designer 2013 Workflow Error photo SharePointDesigner2013WorkflowError3.jpg

Edit Workflow in "Text-Based Designer" in SharePoint Designer:

SharePoint Designer 2013 Workflow Error photo SharePointDesigner2013WorkflowError4.jpg

SharePoint Designer 2013 Workflows Permission Error

SharePoint Permission are very important, and permission for SharePoint Designer 2013 Workflows are very very important. You can get very strange looking workflow errors if you don’t configure your permission correctly.
SharePoint Designer 2010 Workflow error photo 2.jpg


First thing you need to know:

The initiator of the workflow shouldn't be the System Admin account, because it most likely going to give issues.

Workflow permission:

The user who is initiating the workflow must have access to the all the place the workflow touches.
  • If the workflow creates a task or list item, the initiating user needs to have access to that list.
  • If the workflow has a “Log to History List” action, the initiating user needs to have access to the "Workflow History" list ([site name]/Lists/Workflow%20History)

Wednesday, 12 June 2013

Installing .net Framework 3.5 service pack 1 on Windows 8

So today, I had an issue getting into SharePoint Designer 2010 from my newly installed Windows 8. First I did all the windows updates and it still didn’t work. I downloaded the Microsoft file “dotnetfx35”, I tried every version. They all failed.

I finally found this article: http://www.diginks.info/2013/03/install-net-framework-35-in-windows-8.html , method 2

So basically:

  1. You need to insert the Windows 8 installation disk (e.g. disk drive "e”)
  2. Open command prompt as the administrator
    a. Open search
    b. Type “cmd”, on the right
    c. Right click on “Command Prompt” and click “Run as Administrator”, at the bottom
  3. Run this script:
    DISM.exe /online /enable-feature /featurename:NetFx3 /All /Source:e:\sources\sxs /LimitAccess