Pages

Showing posts with label SharePoint 2013. Show all posts
Showing posts with label SharePoint 2013. Show all posts

Friday, December 13, 2013

SharePoint Document Sets - A real world example

Document Sets are awesome!

During my assignment at an asset manager in the Netherlands, I really started to appreciate the power of Document Sets in SharePoint. I never really was a big fan (not sure why exactly) and never used them. One of my colleagues from the Intranet Team showed me the benefits and now I think they rock! I recently wrote an article for the DIWUG E-Magazine where I also write about Document Sets. In this post I would like to show you an example of the use of Document Sets within my own team at Macaw. Let's take a look!

Storing publications and presentations

Our department finds it really important to share SharePoint knowledge by writing internal or external publications. We store the publications in Document Sets. The following screenshot isn't an actual representation of our use of Document Sets but gives you a good perspective:


The publications are grouped by SharePoint version. Each visitor can immediately search for the SharePoint version they are looking for and also get a glimpse at the author. Let's create a new publication:


Every author has to attach metadata to the publication. This improves the Search results and every visitor gets all the details of the publication. After entering all the metadata the following screen appears:


This is what I love about Document Sets! The welcome page. You see a description and all the important metadata such as the URL of the publication. I hope you noticed a different view compared to the library, where the document sets are grouped by the SharePoint version. The content of the Document Sets has a different view and different metadata! Awesome! This is why I recommend using Document Sets instead of folders, you have a lot more flexibility and options. It really improves User Adoption of SharePoint and Document Libraries. So how do you recreate this solution? It's really easy.

Content type and site columns

We start by creating a new Content Type based at the default Document Set Content Type:


We create new site columns or attach default site columns to provide the metadata of our Document Set. Create a new document library and attach the Document Set Content Type:
  • Click on Library in the ribbon
  • Click on Library Settings
  • Click on Advanced Settings
  • Select Yes to allow the management of Content Types
  • Click on Ok.


The Document Set is now available in our library.

Document Set Settings

A Document Set has very useful settings. Let's take a closer look at these settings:

Allowed Content Types

This settings enables you to set the default Content Types within the Document Set. I don't recommend using this feature because it doesn't work properly. Let me show you. I select a Document Content Type called Fact sheet as my only allowed Content Type. This is what happens: 



The Fact sheet appears under New Document but after uploading a document the following happens:


In case the document library contains more Document Content Types the default one is selected. I recommend using the Default Content option.

Default Content

The main reason you want to use the Allowed Content Type feature is because you want your end-users to create Document Content Types with a predefined template. There is an easier way to do this. That's using the Default Content option. You can add templates here, these templates are automatically added to the Document Set after an end-user creates a Document Set. Very handy!  

Shared Columns

Again, a very cool feature. By adding Shared Columns all the document inside the Document Set inherit the Document Sets metadata. I really recommend using this feature because it improves the Search results in your SharePoint portal.

Welcome Page Columns

You probably noticed the metadata fields at the welcome page right? 



How can I display those metadata fields? By using this feature!

Welcome Page View

Also a very powerful feature to display different metadata inside the Document Sets compared to the view of the Document Sets in the Document Library. We first have to change the default All Documents view to group by the Document Sets based at SharePoint version and only show the Author field:



To set a dedicated view for the Document Set we have to create a new view:



So how do we get this view to be the default view for the Document Set? By selecting it at the Welcome Page View option.

This is how Document Sets can benefit your business. I really hope you found this post useful and you can start working with Document Sets in your business.

Friday, November 22, 2013

SharePoint Connections Amsterdam 2013 - My presentation

I was very proud to be part of SharePoint Connections Amsterdam 2013. Its a great conference with amazing speakers and sessions. I talked about Best Practices Document Management in SharePoint (Online) 2013. You can find my presentation by clicking here or watching it here:



Don't hesitate to contact me with any questions.

From File Shares to Document Libraries

I wrote an article for the latest DIWUG E-Magazine. Click here to download the magazine in PDF format. The article connects with the webinar I did last September and my presentation at SharePoint Connections Amsterdam 2013. This is the introduction of the article:

"End-users love their files shares with folders, there I said it! There’s no denying it. They really
do; why you may ask? They have been working with folders for many, many years. It has
become a familiar face staring back from the monitor screen. End-users also find folders easy
to use; they know where to find their documents, even if this means browsing through many
layers of sub folders. Let’s be honest: it’s really easy to create new folders, pretty much child’s
play. That’s fine for them because they are used to it and have accepted this working method.
And here you show up, telling them folders are bad! Very bad! Metadata is the new cure for
finding and structuring documents by creating new columns, views, applying a taxonomy and
maybe even document sets (isn’t that a folder?). Just remember the look on your end-users
faces, when you are explaining this, because they aren’t buying it. This is a very common
scenario for every SharePoint Consultant. I have been there many times before. By writing
this article, I want to help you convince your end-users of the power of SharePoint Document
Management with useful tips and tricks."

I hope you enjoy the article and find it useful.

Wednesday, November 6, 2013

SharePoint and Yammer - The Yammer app

The Yammer App for SharePoint (Online) 2013

In this post I want to discuss the Yammer app for SharePoint (Online) 2013. The app has been available for a while (since June) but I never really got around to try it out! Since my previous two posts about the Yammer and SharePoint integration (click here and here), I am really interested in this integration and the possibilities it offers for the business. Let's take a closer look how the app works.

Installation process

I start by installing the Yammer App. I have to browse to the SharePoint Store:


The app is free and the only thing I have to do is click on Add it:


The installation process only takes a couple of minutes. After its done, I click on the Yammer tile:




The App has three feed options: Group, Home and Comment. Before we can choose a feed, I have to sign in:


I need to sign in once and approve the trust between my Yammer account and the SharePoint site:




The trust is enabled and I can choose a feed type:

Group feed


I have to select a Yammer network and an Group ID. The pop-up gives you a description how to obtain the ID. Got the ID? The feed appears:


This feed can be used when a team or department has a related Yammer group. For example, the Contoso Sales team discusses sales updates in Yammer and also have a SharePoint team site to store their documents. You can add the Yammer App in the SharePoint Sales team site. The users have the option to add new messages from Yammer:


The message appears very quickly in the Yammer SharePoint App:

Every user can also add messages, no surprise, from the app to Yammer.

Home Feed


To change the feed type an user with full control or contribute permissions can click on the wheel icon on the top right corner of the web part. This is something I will discuss further in this post but for now I will focus at the feed itself. I have to select one of the Yammer networks related to my account to view the home feed of that network:



Comment feed


The comment feed is comparable to the new Post feature. I can create a Yammer page to talk about any SharePoint object such as documents, pictures, sites or pages. For example:


After entering the link to the time-off policy document, Yammers creates a comment page:


The Post feature is really aimed, for now at least, at documents. By using the comment feed you can also discuss other interesting and valuable SharePoint objects. 

Issues

Although I really like the Yammer App and the features it offers, I have a couple issues with it.

Firefox 
My Firefox browser didn't like the Yammer web part at all! It's really unstable because it didn't show the sign in button:


Videos
I posted a link to a video in Yammer and a preview is generated. This preview disappears in the feed of the App.

Permissions to change the feed
I found it very unusual that every SharePoint user with contribute permissions is also able to change the feed of the web part. I can imagine that every site owner wants to display one feed and not letting users with contribute permissions change this themselves.

Wednesday, October 23, 2013

Internet Explorer 11 and SharePoint 2013 issues

After updating to Windows 8.1 you automatically get Internet Explorer 11. Sounds nice right? Its not!


The new Explorer causes serious issues with SharePoint (Online) 2013:


  • Calendar web part is extremely corrupted
  • You will click Settings > Edit Page, Pages will not enter edit mode.
  • Web Part Properties cannot be modified.

Thanks to Bojan Buhac I found the workaround to fix these issues:

  1. Click Compatibility View Settings in Settings
  2. Click Add to add the current SharePoint site to your list.
Thanks dude! This is very embarrassing for Microsoft and a massive #FAIL!

Source
http://sharepointthing.wordpress.com/2013/10/09/problem-with-sharepoint-2013-and-internet-explorer-11/

Tuesday, September 17, 2013

How to create an organizational chart with SharePoint and Office 2013

I wrote a guest blog at the ShareGate forum about creating an organizational chart with SharePoint and Office 2013. Check it out by clicking here.

Wednesday, September 11, 2013

SharePoint 2013 Search Query Tool

I can really advise to download the following tool:

SharePoint 2013 Search Query Tool

A great tool to actually see if your managed properties are actually crawled and what else gets crawled. Really saved my life with a recent project!

Monday, September 2, 2013

SharePoint 2013 - How to hide the default searchbox

One of our customers wanted to hide the default search box at the top right side of the screen but only for the home page! Instead of creating a separate Master Page a colleague of mine (Maarten van den Dungen) recommended adding a Content Editor Web Part with the following code:

<style type="text/css">
#titleAreaBox #SearchBox {display: none !important;}
</style>

Before:



After:
Hope you find this useful for your SharePoint projects.

Monday, August 26, 2013

SharePoint 2013 Managed Metadata navigation - End users cannot see the top navigation

For one of our customers I decided to use the Managed Metadata navigation feature. This is a really cool new feature in SharePoint 2013. I did encounter one issue reported by the administrators. Apparently the end users weren't able to see the top navigation. Strange! Let's take a look at an example I created to explain the problem.


The top navigation in this site is created by using a term set:



Every term can point to a location in SharePoint, for example a site:


I did this for all the sub terms: Subsite A and Subsite B. Apparently that's not sufficient! The main term also needs a location. After I added a location the problem was solved and the end users were able to see the top navigation.

Monday, August 19, 2013

5 reasons to use the Office Web Apps in SharePoint 2013

Personally, I really like the Office Web Apps feature and always recommend it to our customers. I would like to share the five top reasons to use the Office Web Apps:
  1. Search and document preview and deep refiner
  2. Tablets
  3. No local Office client needed
  4. Speed
  5. Creating new Office documents in the browser
Let's take a closer look!

Search and document preview and deep refiner

A preview of an Office document is visible in a document library or search results. The end user can see immediately whether this is the correct document through the option to zoom in and out of the document. This saves precious time! The above screenshot shows a header called Take a look inside. The first five chapters of the Word document are clickable and directly open the document corresponding to the selected chapter. This feature also exists for PowerPoint presentations.

Tablets
A requirement for working with Office Web Apps in SharePoint 2010 was an installation of Microsoft Silverlight. On an iPad or Android tablet it isn't possible to install Silverlight. This was an obstacle to the use of SharePoint 2010 on an iPad or Android tablet (without third party apps). The 2013 version of Office Web Apps is no longer based on Silverlight. This means that Android tablets and the iPad can open and edit documents using the local browser. This supports the use of Bring Your Own Device and working with mobile devices at the workplace.

No local Office client needed
Since an Office document using the OWA opens in the browser, an end user doesn't need to have a local Office client. The end user can open an Office document from any location (home PC, tablet, Internet cafe). There are also no restrictions based at the Office version. You can open a 2007, 2010 or 2013 Office document in the browser.

Speed
Opening an Office document via the browser is much faster than opening an Office document in the local Office client.

Creating new Office documents in the browser

SharePoint 2013 in combination with Office Web Apps makes it possible to create new Office documents with the browser. Office documents are directly stored in a document library. In SharePoint 2010 you had to choose one Office template while creating a document library, in SharePoint 2013 all templates are available.

In SharePoint 2013 you need a separate server to install the Office Web Apps. A previous post of mine contains more cool features of the Office Web Apps. You can click here.

Hope you find this post useful, don't hesitate to leave any feedback.

Friday, June 28, 2013

SkyDrive Pro apps for Windows 8 and iOS

Finally! The Windows 8 and iOs apps for SkyDrive Pro are here. That's really exciting news.

Click here to read more information about it. For our Microsoft fanboys this is link to use ;-)

Enjoy!

Thursday, June 27, 2013

SharePoint 2013 - Create your own display template

I am working on a project where I want to use the Content Search Web Part. I need to show more fields in the results so the default display templates weren't sufficient. Through a colleague I found this awesome video:




This really helped me! Thanks a lot Erik! You rule :D

Wednesday, June 5, 2013

SharePoint 2013 Site Mailboxes - Limitations

I am a fan of the new Site Mailboxes feature but there are some serious limitations. Apart from the fact a new license is used when creating a site mailbox, I found a whitepaper with a nice summary of the limitations:

No tagging of content with Metadata
  1. No provision to capture email attributes from originating email when saving specific email attachments
  2. No provision to capture email attributes when saving emails
  3. No ability to tag content with custom metadata
  4. No ability to select a library content type
  5. No validation of metadata, files are saved checked-in
  6. No ability to rename a file when saving to SharePoint
  7. No support for versioning documents. If a document is saved to a location where a document of the same name exists, the save will fail and the user is notified accordingly via email.

Limited integration with File Explorer and other Office applications
  1. No unified view of Site Mailbox locations from Microsoft Office (Word, Excel and PowerPoint) when saving and tagging with metadata
  2. No unified view of Site Mailbox locations when saving files from File Explorer

Limited access to SharePoint capabilities when viewing content
  1. No easy way to switch to a SharePoint view of the library content
  2. No mechanism to View/Edit the selected items properties

Limited attachment and Link Management
  1. No facility to replace attachments with links
  2. No support for using document ID’s when inserting links
  3. No ability to insert SharePoint/Site Mailbox content as attachments when sending to external recipients

Technology Restrictions
  1. Only available when using the full 2013 server technology and associated prerequisites.
    • SharePoint 2013 / Office 365
    • Exchange 2013
  2. Requires a Site Collection be configured to use HTTPS
  3. Site Mailboxes are only available to the end users within Microsoft Outlook 2013
  4. Hard limit of 10 Site Mailboxes within Microsoft Outlook.
Please click here to download the whitepaper.


Friday, May 24, 2013

Integrate Bing with SharePoint (Online) 2013 Search

I really love the new Search engine in SharePoint 2013 (including SharePoint Online 2013) and I said if before and will do it again:


"SharePoint 2013 Search out-of-the-box rocks!"

You can find the blog post where I explain my love for SharePoint 2013 search by clicking here. In this post I want to show you how east it is to integrated Bing Search results with the SharePoint search results. Why Bing and not Google, you probably wonder? That's because Google doesn't support the OpenSearch protocol anymore. Although Google is an awesome Search engine we need to show some love for Bing as Microsoft fan boys ;)

What does this look like? Let's take a look at the following example:


I searched for marketing campaign content and in the result block five Bing Search results are shown. I can even click on Show More to see all the results:


Pretty cool right? Let me show you how to configure the integration with Bing! Start by clicking on Site Actions, Site Settings, Result Sources and New Result Source. Enter the following information:

Name
Bing Search Results

Description
This is an optional field. You can use it when more people configure Search to let them know what the Result Source is being used for.

Protocol
OpenSearch 1.0/1.1

Query Transform
{searchTerms}

Source URL
http://www.bing.com/search?q={searchTerms}&format=rss&Market=en-us

Credentials Information
Anonymous

Click on Save and your Bing Result Source is ready! The next step is creating a Query Rule. I always use the following example in my presentations and demo's:

"Contoso has a large marketing department with a lot of relevant content on the Contoso SharePoint portal. Although a lot of marketing content is available there is of course more content on the Internet. The marketing department wants to automatically search Bing when people search for marketing content."

We need to create a Query Rule that responds to the word marketing to launch a Bing Search. Go back to Site Settings and click on Query Rules. Select Local SharePoint Results and click on New Query Rule:

Rule name
Marketing 

Query Conditions
Query Contains Action Term Action and Action Term is one of these phrases: marketing

Actions
Add Result Block
Block Title: Bing results for "{searchboxquery}"
Configure Query:{searchboxquery}
Search this Source: Bing 
Items: 5
"More" link goes to the following URL: http://www.bing.com/search?q={searchboxquery}

Now click on OK and Save. Your query rules is ready and Bing Search results are displayed when the word marketing is used in a Search query. Do you always want to use the Bing Search results? Just leave out the Query Conditions. 

Thursday, May 16, 2013

SharePoint 2013 - Promoted links app missing

I saw a question on Twitter and the TechNet forum from people who couldn't find the Promoted Links app. A while ago I wrote a blog about this great new app. You can find it here.

To find the app you need to enable the following feature:

Team Collaboration Lists

Hope this helps.

Monday, May 13, 2013

The SharePoint 2013 Handbook: An insight by the SharePoint community

I am proud to be the co-author of a new SharePoint 2013 book:

The SharePoint 2013 Handbook: An insight by the SharePoint community

I wrote three chapters for the book:

  1. External Collaboration with SharePoint Online 2013
  2. Building Communities
  3. Search in SharePoint 2013 Rocks

My next goal is to write a book by myself :-)

Monday, April 29, 2013

SharePoint Saturday Belgium - My presentation

I had a great time at SharePoint Saturday Belgium and was proud to be a speaker! The organization did a great job because it was a great event with many awesome sessions :-)

I added my presentation at Slideshare. You can view it here below:

Tuesday, March 5, 2013

SharePoint 2013 - Keywords, tags and #hash-tags

The reason I am writing this article is the introduction of #hash-tags in SharePoint 2013. I was curious about the relationship with the existing Tags and Notes feature. What was the impact? Do we only have to use #hash-tags or also Tags and Notes? Wait, we also have keywords! Are you confused? Believe me, you aren't the only one! Just keep on reading.

Tags and Notes and SharePoint 2010
SharePoint 2010 came with a new feature to tag content, or leave a note, such as documents or sites:



There were three advantages by using tags:
  1. Mark your favorite content or sites
  2. Improve search results
  3. Connect with people
Mark your favorite content or sites
Tags and Notes were visible in your My Profile page:


All the related content to a tag was displayed. This could be used as Favorites comparable to bookmarks in any Internet browser.

Improve search results
Tags were indexed by search and could be used as refiner:


Connect with people
Every Tag has its own profile page:


This page enabled people to connect with each other by leaving notes and discuss the related content.

SharePoint 2013 is here!
This was a brief history lesson because now we have SharePoint 2013. What has changed? Let's take a look.

The Tags and Notes button isn't really visible anymore. In SharePoint 2010 the button was prominently available at the top right of the screen. This button is gone in 2013. To tag a document you really have to search for it! You have to select the document, click Files in the ribbon and at the right side you can find the button. You would expect the option to be available in the new call out menu but unfortunately it's not:


After leaving a tag with a document you expect to view the tags, just as in SharePoint 2010, in your My Site. You probably know by now that the My Site has changed. There is no more a My Profile page and all the tabs are gone. The home page of Newsfeed contains an overview of elements you are following:


Aha! Tags, that must be it. Let's click on the number 3:


Hmm, that's not it. Those are #hash-tags. OK, that is confusing. So were are my tags? I checked every item in the quick launch but no Tags and Notes to be seen! I asked on Twitter if anyone was familiar with this. A SharePoint Community member called Thomy Goelles told me to add the following URL in the Newsfeed:

/_layouts/15/thoughts.aspx  

This worked! The page is back but wait, why is it so hidden? That is not a good sign at all. I decided to compare the situation with SharePoint Online 2013. The About Me page actually contains a link to Tags and Notes. Why the difference? At the moment of testing SharePoint Online 2013 was still in technical preview mode. I decided to contact Microsoft support and they told me Tags and Notes is not deprecated. I had the add the tag cloud web part. Strange but this did the trick. I believe when an administrator adds the web part this automatically adds it for every user in the farm.

Keywords
Every library in SharePoint 2010 had the option Enterprise Metadata and Keywords Settings. This enabled an extra column in a library to leave a tag. I liked this feature because its really easy to use for end users and it improves the search results. The keywords were basically the same as a tag. The keywords appeared in the Tags and Note profile page and had the same features as tags. 

You are still able to use this option in SharePoint 2013. Although my keywords did not appear in the Tags and Notes page. The tags did appear in the Term Store Management under Keywords. I am not sure what the purpose is of keywords when they don't appear in the Tags and Notes overview.

#Hash-tags
Now we got another method to tag content: #hash-tags. That makes three different options: tags, keywords and #hash-tags. What do hash-tags accomplish? For starters you can use #hash-tags in the Newsfeed:



I decided to add a #hash-tag with a document. The #hash-tag appears in the Tags and Notes page ans has its own profile page:


Why would there be such a page for a #hash-tag? Because we already have one connected to the Newsfeed:


Comparable to the Tags and Notes profile page but aimed at conversations. The page contains a link called Tagged items. This never did anything for my environment. No results at all, even after using a #hash-tag with a couple of documents. 

Conclusion
There are to many options at the moment. Microsoft has to make a decision. Leave out Tags and Notes and only work with #hash-tags or make sure #hash-tags are only used in the Newsfeed.

My advise is to use Tags and Notes for documents and #hash-tags only in the newsfeed.

Saturday, February 23, 2013

SharePoint 2013 - Resources

Wednesday, February 20, 2013

SharePoint 2013 - Managed metadata and Quick Edit

The datasheet view has always been a great asset to document libraries. It was really easy to change the value of multiple documents instead of editing every single document separately. If you upload multiple documents in a document library with custom metadata, SharePoint never asks to assign custom metadata to the documents. This means that you have to edit every single document or use the datasheet view. New to SharePoint 2010 was the term store with its taxonomy features. To use a taxonomy within a library you had to use a managed metadata column. This column wasn't supported in the datasheet view in SharePoint 2010!

This finally changed with the release of SharePoint 2013. The name Datasheet View changed to Quick Edit but who cares, so long we can edit managed metadata. Let's take a look how this works:


We have three options:
  • Replace all selected values with these items
  • Add these terms to all selected fields
  • Remove these terms from all selected fields

Replace all selected values with these items
You can select multiple fields and replace the current values with a new one.

Add these terms to all selected fields
You can select multiple fields and add a new value.

Remove these terms from all selected fields
This one works in strange ways. You have to select the fields and choose the current value to remove the selection. Why not just use the delete button?

The Quick Edit also support suggestions so you can start typing and select the term of choice. Finally!