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.
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?
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? (more…)
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.
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. (more…)
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. (more…)
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.
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: appsadd-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. (more…)
It’s never a bad thing to look at what’s coming. This future peeking seems to be hot in the SharePoint world, with guys like Dan Holme, Benjamin Niaulin and Daniel McPherson giving their take on what’s in store for us. Interesting views which of course always include things like cloud, mobile devices and new ways of working for your end users, whatever generation you want to call them.
In my day-to-day work though, I am still mostly involved with enterprise grade customers who might be thinking about that stuff, considering it, but most definitely they’re not there yet. On the contrary; they have a long way to go. So I wanted to write this post to give an overview of things those companies can do today with their current landscape, in order to prepare for that future. And do not worry: the conclusion will not include you writing apps from now on.
In this n-part blog series, I’ll discuss some of the ‘hot topics’ and my views on what choices enterprise grade companies need to make.
It seems this issue arises in almost every migration project: “Hey, we have a bunch of HTML based files which we’ve uploaded to SharePoint, but now they don’t work any more!”. With “don’t work”, usually it means the user is prompted to download the file instead of being able to just view it in the browser. So it’s working, but the end result is not what the end-user expects. Also, “a bunch” is usually a couple of hundred files which were exported from some legacy application a few years back and have been sitting on a file share or in SharePoint 2007 ever since. (more…)