Tag: sharepoint

Favorite articles about the Ignite 2018

Hello 🙂

If you are like me and didn’t get to go to Orlando to attend the Ignite sessions, this post is for you !

First of all, know that not all is lost since we can watch the recorded sessions here .

It’s as if we are almost there right ?! Almost 🙂

Second, you can read the technet articles summing up the most important announcements. Here are some of my favorites:

  1. StaffHub to be retired : Here
  2. What’s new in Teams, Ignite Edition: Here
  3. OneDrive announcements at Ignite: Here

Enjoy 😉


Future of SharePoint 4 May


Voilà un résumé de la présentation Future of SharePoint Conference qui était très intéressante : https://vts.inxpo.com/Launch/Event.htm?ShowKey=30784

SPOILER ALERT : Attention, pour ceux qui prévoient de voir la vidéo ne continuez pas à lire, ce post est plein de spoils concernant les nouveautés SharePoint/O365 prévues pour 2016. :).

Parmi les choses prévues : Refonte de l’onglet « Sites » et mise à disposition d’une nouvelle application mobile : Votre Intranet dans votre poche. L’application se base sur les sites SharePoint existants pour remonter les news et les dernières activités (infos similaires à Delve)


Refonte de l’onglet « Sites » en « SharePoint » : on présente les activités recentes de chaque site


Refonte de la page d’accueil du teamsite : on met en avant une nouvelle page par défaut avec les news et les activités (les dernieres remontées par Office Graph). + création de composant simplifiée…3

Création de page dans le site à la mode Sway (accessible sur n’importe quel device)


Refonte de la présentation d’une liste SharePoint. PowerApps est livré avec et permet de définir des flows entre les briques (cf. bouton Add flow dans le ruban)


La nouvelle présentation des bibliothèques (homogène avec l’expérience OneDrive) avec entre autres une gestion simplifiée des colonnes, une présentation en mode flat avec vignette, la possibilité de mettre à jour simplement les propriétés, …


Pour les développeurs, la mise a disposition d’un Framework SharePoint (framework javascript) pour créer des pages et des webparts


Pour plus d’infos sur la partie dev, s’inscrire a la newsletter : http://aka.ms/SPdevProgram

Enfin, afin de mettre à disposition les innovations SharePoint, sur les environnements On Premises 2016, à un rythme plus régulier, Microsoft annonce les :


Task Checklist for Testing Web Parts

The following sample SharePoint specific checklist contains a series of tasks designed to help you determine the quality of Web Parts you are asked to deploy or maintain.  This can be used in addition to the tests, or it can be used as a simplified alternative depending on your organizational needs.

Task Checklist

Verify that you can add the Web Part properly to a Web Part zone.
Verify that static Web Parts render appropriately and do not cause the Web Part Page to fail.
Verify that the Web Part works correctly regardless of where the Web Part Page is located.
Verify that every public property can handle bad input.
Verify that the Web Part handles all of its exceptions.
Verify that the Web Part renders correctly in SharePoint Designer.
Verify that Web Part properties displayed in the tool pane are user-friendly.
Verify that the Web Part appears appropriately in the web part gallery.
Verify that the Web Part previews properly (through the web part gallery).
Verify that you can import and export the Web Part properly.
Verify that Web Part properties are not dependent on each other.
Verify that Web Parts work correctly with different combinations of Web Part zone settings.
Verify that the Web Part renders appropriately based on user permissions.
Verify that adding several instances of the same Web Part to a Web Part Page (or in the same Web Part zone) works correctly.

Hands on labs for Sharepoint 2013

Hello 🙂
I HAVE INCLUDED A FEW OF THE SharePoint 2013 Labs hat are available for download. I hope everyone can make the time to download the LABs and walkthrough them, as this will give you a better Idea of the new features in SharePoint 2013

Test Lab Guide: Demonstrate SAML-based Claims Authentication with SharePoint Server 2013

This paper provides a brief introduction to SharePoint Server 2013 and illustrates how to create a three-tier test lab that uses SAML-based claims authentication.
Test Lab Guide: Demonstrate Intranet Collaboration with SharePoint Server 2013

This paper helps you configure an environment to demonstrate the intranet collaboration features of SharePoint Server 2013.


Test Lab Guide: Configure SharePoint Server 2013 in a Three-Tier Farm

This paper provides a brief introduction to SharePoint Server 2013 and illustrates how to create a three-tier test lab.


Test Lab Guide: Demonstrate Forms-Based Authentication with SharePoint Server 2013

This paper explains how to configure and demonstrate form-based authentication for SharePoint Server 2013 based on the Test Lab Guide: Configure SharePoint Server 2013 in a Three-Tier Farm (http://www.microsoft.com/en-us/download/details.aspx?id=30386).
Hands-on Lab Online: Advanced Web and Worker Roles


Hands-on Lab Online: Introduction to Windows Azure Virtual Machines


SharePoint Composite Handbook

A SharePoint Composite combines data, documents, and business process in a useful, productive way by assembling, connecting, and configuring the basic building blocks of functionality available in SharePoint 2013 and Microsoft Office 2013 so you can rapidly create business solutions.


Enjoy 😉

Problem saving documents edited in visio in sharepoint 2010

When the users open a visio document (from a sharepoint 2010 library), make changes and try to save they get this error…

Unable to get value of the property ‘eDocument’: object is null or undefined
URL: http://ourserver/_layouts/1033/bform.js
Do you want to continue running scripts on this page.

I have googled and found posts that suggest overwriting/adding js code from previous SP versions to this file in 2010 but I’m not sure that is a good idea.

When the doc properties are viewed there is missing mandatory data that was previously there before they tried to edit/save the document.

Somehow something is removing mandatory metadata and the getting itself confused.

This is not specific to a single document or library – it is consistent across the site collection

No other office docs have this problem.
Visio is set to open in the client application

Any help will be appreciated
Thank you

SharePoint: extending the security trimmed control for groups

SharePoint: extending the security trimmed control for groups

Hello everyone 🙂

In SharePoint, there is the SPSecurityTrimmerControl, used to show some part of the page to only certain users. The criteria filter is based on SPBasePermissions. But what if you want to consider groups also? You can derive from SPSecurityTrimmedControl and override the Render method with your own logic, as described in the article Extending the SharePoint Security Trimmed Control to support SharePoint Groups

Content type publishing option missing from Site Collection Administration

Okay, you have set up your content type hub, published your content types and are now ready to use them in your lists and libraries. You go to your list, click to add from existing content types and your published content types aren’t available.

You may find this if the top level site in your site collection was created from the Blank Site template (there may also be other templates out there where this doesn’t work too). This is because the TaxonomyFeatureStapler feature does not include the Blank Site template.

You probably don’t want to go back and recreate your site collection again, so you can activate the feature manually by typing the following stsadm command:

stsadm -o activatefeature -id 73EF14B1-13A9-416b-A9B5-ECECA2B0604C -url http://toplevelsiteurl

Once activated, you will see the Content type publishing option appear in Site Collection Administration, as well as the Term store management option in Site Administration on the top level site. You should now be able to use your published content types as required – even in sub-sites (if not, you can repeat the stsadm command for your sub-sites, too).