Tag: #SharePoint

[O365] Synced security group member without permissions in SharePoint

June 27, 2017June 22, 2017 Jasper Leave a comment

Had a strange thing happen at my client yesterday. We were working on an Office365 set-up and had created some AD security groups in order to have reusable permission groups across a bunch of SharePoint site collections. We missed one person in the org due to which she was not able to access a site she was supposed to have permissions to. So we added here, but still she couldn’t access the site… weird…

TL/DR version: rebooting the machine fixed the problem. If your first response is: “huh?”, read on…

[Azure] From Function to SharePoint List Item

January 2, 2017January 1, 2017 Jasper Siegmund 5 Comments

This article describes how to insert an item into a SharePoint list using an Azure Function written in C#. Might seem like a trivial task, but there are some caveats you might want to take notice of before you start.

[SPO] Creating a ‘modern’ homepage on an old team site

October 24, 2016October 24, 2016 Jasper Siegmund Leave a comment

If you’re an Office365 user, you will probably have noticed by now that the new look & feel dubbed ‘modern’ (which is a stupid name, but aight…) is slowly but steadily making it’s way into more and more parts of the overall experience. I like the modern look. It’s crispy fresh, more in-line with modern UI’s like Googles Material and Microsofts ~~Metro~~ Modern UI. As an added benefit, the new look should play well with the SharePoint mobile app, bringing responsive design to the table so pages remain usable on mobile devices.

But what about legacy sites?

[O365] Deploying a SharePoint theme / branding using JavaScript only

June 7, 2016June 7, 2016 Jasper Siegmund Leave a comment

With provider hosted add-ins being introduced in SharePoint 2013, the world of SharePoint devs shifted to using provisioning schemes to get their stuff in SharePoint sites. And this worked, quite well i might add. You might have read my post on SPMeta2 vs PnP (which is a bit outdated I must add). These provisioning engines allow your to provision “stuff” (files, folders, lists, contenttypes, whatever) to SharePoint. Amongst other things, they have one thing in common: they’re built on top of the CSOM (Client Side Object Model) C# SDK. This means that you are forced to run them as a stand-alone task, or deploy a provider hosted app which includes having a server up and running somewhere. So what if you do not want that? Read More

[O365] Parallel processing and CSOM; friends or foes?

September 7, 2015September 7, 2015 Jasper Siegmund 9 Comments

In the project I’ve been working on the last few months, we had to import some list items and file into SharePoint coming from a legacy application which is being replaced by SharePoint Online. There is plenty of guidance available on how to do this, it boils down to using the CSOM API’s to upload documents and create list items, set metadata, etcetera. But when volumes start growing, so does the pain because these actions are usually not that fast. So whilst your process is waiting on a file to be uploaded, why not do something in the meantime? Well you can with some parallel programming magic and it isn’t even that hard, but there are some caveats you need to take into account.

[SP] Constructing a “Manage site metadata navigation” link

July 10, 2015July 10, 2015 Jasper Siegmund Leave a comment

If you’re aware of Managed Metadata Navigation, you might also know the hyperlink within the navigation settings which allows you to edit the sites’ navigation termset. Now first thing you should know is that that link is often broken out of the box. When you click it, you *should* only get the navigation termset and nothing else. But more than often, you’re taken to the full termstore manager displaying everything instead. Read More

[O365] SharePoint Content Search webpart is not being indexed

April 14, 2015April 14, 2015 Jasper Siegmund Leave a comment

Thinking of a title for this post, I wanted to start with “Inconvenient” because that pretty much describes the essence. Inconveniently enough that trademark has already been claimed by an MVP you might know if you ever search for anything SharePoint related (shout out to Waldek!). Anyways, as inconvenient as this all is, let’s get started. Read More

[O365] Some tagging field(s) could not be found

April 9, 2015April 9, 2015 Jasper Siegmund Leave a comment

I ran into a stubborn error message trying to connect to a catalog list defined on another site collection. The error was:

Some tagging field(s) “owstaxidSector,owstaxidRegion,owstaxidProductx0020Class,” in the shared catalog could not be found in search schema.

Now when I checked the catalog site search schema (can be found under Site Settings -> Search -> Schema), those columns weren’t there. So: valid error message. But why weren’t they? I had created the site columns, added them to a content type, put the content type in the catalog list and I was perfectly capably of selecting them in the catalog settings.

This is a little SharePoint gotcha: a column will only get created as managed property in search when SharePoint finds actual values for it during an indexing run. So when you create your list, create at least one item in it which has values for every single field you want to use as a managed property in search. You can delete that item afterwards if you want to, search won’t delete the managed property.

[SP2013] SharePoint add-ins in DR farms

March 25, 2015November 23, 2015 Jasper Siegmund Leave a comment

When setting up a second SharePoint farm for disaster recovery purposes, there are all kinds of things to take into consideration. Most of those are perfectly covered in other blogs and on TechNet.

With the new ~~app~~ add-in model though, there is one additional factor to take into account: ~~apps~~add-ins! When in case of a disaster you need to switch operations over to your second farm, you want your add-ins to remain working. And there’s some stuff you need to take care of to make sure they do. Read on to find out what. Read More