Wikipedia states that SharePoint is a web-based collaborative platform that integrates with Microsoft Office. Launched in 2001, SharePoint is primarily sold as a document management and storage system, but the product is highly configurable and usage varies substantially between organisations.
According to Microsoft, SharePoint 2013 makes it easy to work together securely on documents and team projects. SharePoint lets users explore features and support options that are available for SharePoint, and get tips for using SharePoint to manage your teams and projects efficiently.
In this category, learn everything from troubleshooting SharePoint 2013 to
Digital transformation and beyond.
Therefore, this category is full of handy tips, tricks, advise and How To videos specifically for SharePoint 2013 users. Check out some of the Step by Step features, expert blogs, eBooks, How To videos and webinars.
The main reason SharePoint users don’t pay a great amount of attention to SharePoint file names can be resumed in just one word: Metadata. Since SharePoint allow us to describe every property of a document in its separated column’s metadata, we consider that the file name itself is left with almost no significance.
European SharePoint Community Award Winners 2015
I’m in the midst of two different major workflows for clients right now, one of them being an HR New Hire Onboarding request and approval process. One small but critical requirement of the process was that each level of approval needed a two business day wait period. I’ve seen different suggested solutions for this on the internet, but nothing super easy and in the context of a workflow, or would fully work in my situation. So I thought I’d share a couple of quick and easy ways to accomplish this.
Migrating a SharePoint Website or infrastructure is actually very simple, if you know how your site or infra has been set up. Otherwise, you’ll have many problems during and after the migration. Here are my 14 (hive fourteen ) attention points to take care about heavy customized site/infrastructure migrations from SharePoint 2010 to SharePoint 2013
SharePoint Always-on deployment strategy is an important requirement to achieve high-availability within an organization. SharePoint has broken the barrier within an organization for collaboration, communication, and social network, but the large amount of data analysed and consumed, along with our culture of always-connected has posed a challenge to keep our infrastructure up and running.
SharePoint has many virtues and capabilities but it is not a DAM, MAM, ECM or any other acronym for organising your digital content. Due to the volume of digital content we are creating today and the demands to deliver that content to more platforms, the need for a way of managing this data is essential. Just buying DropBox storage is not the answer and many SharePoint customers end up looking for solutions that are external to SharePoint that do not work with it, or they have to create bespoke integration which costs time and money.
Let’s assume this: you want to create a custom application (e.g. a webpart) that should be used as a Search driven Application. This custom application should display all documents belonging to a predefined content type and it should use the SharePoint search index only to retrieve all matching documents and some of their metadata. One way to start is to have a look on the KeywordQuery object.
Workflows are useful – especially in an enterprise environment. Think of important documents that need to be approved before they get published. In most cases a content approval workflow is used to accomplish that.
Quite often customers ask me about how to create custom Workflow Custom Actions, for SharePoint Designer 2013, using Microsoft Visual Studio. Because on the network there are a lot of contents, some of them not very complete or clear … let me try to clarify this topic, or add some more entropy 🙂 …
In May 2014 I’m going to talk about professional Document Management with SharePoint 2013 at the ESPC in Barcelona and this blog post was intended to be a published right after my session. However, when the ESPC team asked me for a blog post I couldn’t resist to publish this post prior to talking about it.
