Sharepoint-2013

This year of SharePoint Saturday’s started with the one in Munich last weekend. This time there was also a preconference session on Friday. The sessions on Friday and Saturday were held at the brand-new building of Microsoft Germany.

Friday session

This year they organized two preconference sessions. A developer one about Office Dev PnP and an IT Pro about SharePoint 2016. I went to the SharePoint 2016 session where they talked about all the aspects of SharePoint 20116. They started with the architecture and the differences between SharePoint 2013 and 2016. They also explained where the issues were and how to solve them. After the architecture session we went into the authentication options within SharePoint and the hybrid identity. Here we looked at the identity options within Office 365 and the options to get your on-premises users into the cloud. Also, the dependencies where discussed like ADFS on-premises and your local internet line is down. After the lunch break we had a session about PowerShell and the Office Dev PnP PowerShell module that is available for on-premises and Office 365. We ended the day with setting up Hybrid. Thomas did a complete hybrid setup in just 1 hour with some preparations that he did on forehand. The most important part of the hybrid setup of Office 365 is that your identities are available in Office 365. When you have, that part done and your SharePoint farm can talk to the internet you can run a simple wizard from the SharePoint Online admin portal to setup the hybrid farm. This wizard will setup:

Last week I had the privilege to attent Microsoft Ignite in Atlanta. This week was full of news, sessions and a lot of walking. Besides the sessions, this year the expo hall was large, I have spend a lot of time at the expo talking to venders, partners and Microsoft.

I have created a PDF from all my notes. On a few notes I have references to slides, the slides should be come available on https://myignite.microsoft.com/videos. On this site are also all the videos.

This week I will attend Microsoft Ignites 2016 conference in Atlanta. To make it easier for everyone to follow me I have created a OneNote that I will use to share my notes.

You can find that OneNote here: https://arjansp.nl/Ignite2016Notes

A few weeks ago it was the time of the year that the signing certificate of ADFS was expiring. Last year it took us by surprise because the ADFS team did not notify us and we did not put it in our agenda’s that the certificate would expire. So last year we had a lot of people complaining that SharePoint 2013 was not available anymore.

This year we had it in our agenda’s that the certificate would roll over, so we were prepared for a roll over and had contact with the ADFS team and made an arrangement to roll over the certificate. I also found a nice script that can be ran to prepare for the roll over. This script will download the new certificate and when the secondary certificate becomes the primary the script will update SharePoint.

This week I was working with the term store and had to create and import a big chuck of data in the term store. We all know that we have multiple options here

• Just enter them one by one in the browser (great for a few entries)
• Use the csv import
• Use CSOM
• Use Office Dev PnP PowerShell

This post will address the csv import.

Getting started with the csv

For the csv import we have a sample that can be downloaded from the term store (http://“tenant”-admin.sharepoint.com/_layouts/15/1033/ImportTermSet.csv)

Two weeks after my visit to SharePoint Saturday Paris I visited SharePoint Saturday Netherlands. The schedule for today was a bit more relaxed than in Paris. We had 4 session slots of 75 minutes with great sessions and more time in between the sessions to have a chat with sponsors, trying out the HoloLens and playing some games. The HoloLens is a very cool device and I tried it here for the first time.

On May 28th 2016 I visited SharePoint Saturday in Paris (http://www.spsevents.org/city/Paris/Paris2016/). The event was held in the Montparnasse Tower in the center of Paris on the 40th floor. We had an amazing view from that height.

This article contains my notes of the day.

Start of the day

We had some trouble getting in the building because of some regulations of the building owner, but when we were all registered we could go all the way up to the 40th floor. Here we started with a small breakfast, I did not eat in the hotel so I could use this. I came in just after 8 and all sponsors where getting settled because they also had trouble getting into the building. After breakfast and a delay of 15 minutes the first session started at 9:15

Microsoft has released a new framework for developing an awesome front-end called Office UI Fabric. So the big question is why did Microsoft created this framework? We already have a ton of different frameworks for front-end development like Bootstrap, Semantic UI, 960 Grid System and many more.

The short answer is that we did not have a framework for creating Office or SharePoint add-ins that integrates with the looks of Office applications.

Since the introduction of SharePoint 2013 and Office 2013 we as developers have a new option to integrate our applications in SharePoint and Office. The add-in model is in basics just a web application that integrates in SharePoint and Office. Until a few months ago we could not make our add-in look like a part of Office. Andrew Connell wrote a great blog in February of 2015 that we needed guidelines for integrating in Office. The answer to this is the Office UI Fabric that is posted on GitHub.

Some time ago we created a custom retention policy for a customer and last week I had to give some support. I had to dive in it again because I forgot all about it.

Why did we build this?

We build this custom retention policy to move a document to the record center when a specified field has a specified value. This field could be any type of field other than a data time field. The specification of the field and his value was in a list on the root site of the Site collection that the customer can maintain.

There are a number of blogs already written about how to get the Geolocation column on your SharePoint site, but a lot of sites use the wrong syntax for the field XML. Even the MSDN site for adding the geolocation column to your site is incomplete.

The correct XML to use is:

The important part here is the addition of the Name property in the field definition. The complete script to add it to your site is: