Quick Win – Display more view in the selector


Hello everyone,

Today I will inaugurate a new type of post that I want to set up, quick wins.

The purpose of these articles is to show a quick configuration to meet a common business need.


As a user

I want to see more views in the view selector

In order to have more choice without clicking the ellipse


By default, the SharePoint view selector (in classic view) shows only 3 views among the views defined.



By adding a JavaScript on the page, you can display more views. (Replace the 5 number by the number of view you want to display).

ExecuteOrDelayUntilScriptLoaded(overrideSurfacePivotCount, 'clienttemplates.js');
function overrideSurfacePivotCount() {
ClientPivotControl.prototype.SurfacedPivotCount = 5;


Hoping this helps.


Posted in SharePoint 2013 | Tagged , , , | Leave a comment

Fix SharePoint Framework Hello World WebPart

Hello everyone,

Today I will talk about an error that may occur when you try to follow the SharePoint Framework tutorial to create the HelloWorld webpart: https://dev.office.com/sharepoint/docs/spfx/web-parts/get-started/build-a-hello-world-web-part


When you follow the tutorial, using the “gulp serve” command generates the following errors

Error - typescript - node_modules\@types\lodash\index.d.ts(8446,32): error TS1005: ',' expected.
Error - typescript - node_modules\@types\es6-collections\index.d.ts(78,29): error TS2304: Cannot find name 'object'.



The SharePoint Framework evolved very quickly in a very short time. You may have a template version that is not up to date.


To resolve these errors, simply get the last version of the template with the following command

npm install -g @microsoft/generator-sharepoint@latest

If it is not enough,  install the correct versions of lodash and es6-collection via the following commands

npm install @types/lodash@4.14.50
npm install @types/es6-collections@0.5.29

Hoping this helps


Posted in SharePoint Online | Tagged , , | Leave a comment

SyntaxError Unexpected token in JSON at position 0

Hello everyone,

Today I will talk about a problem concerning the use of PNP JS Core on an environment 2013 OnPremise.


Like many I started using PNP JS Core for my developments. After retrieving some information and doing some conclusive tests on an Office 365 environment, I wanted to reuse my code on a SharePoint 2013 OnPremise.

And there .. Boom!

SyntaxError: Unexpected token < in JSON at position 0

The code does not have anything complicated, it will only read the contents of a list.


Looking a bit, I saw that the return of the REST call was XML and not JSON. It seems that this comes from the basic configuration of SharePoint 2013 SP1 https://github.com/SharePoint/PnP-JS-Core/issues/125


The solution to this problem is to pass a configuration before making the call: https://github.com/SharePoint/PnP-JS-Core/pull/127

        headers: {
            "Accept": "application/json; odata=verbose"

Simple but when you start using PNP JS it can be useful to know.

Hoping it helps.

NB : Thanks to Yannick for helping the noobie I was in this situation !


Posted in SharePoint 2013 | Tagged , , , | Leave a comment

ESPC16 Feedback – Part 2

Hello everyone,

Today I will continue on the subject of the previous post by talking about tools that I’ve seen in action at the ESPC16.

QUnit :

JavaScript library for Unit tests:


jQuery Mockjax :

JavaScript library for mocking Ajax calls:


Selenium webdriver :

Available as a Nuget package, it allows ,among other things, to do UI tests by simulating different browsers:


Approval Test :

A tool allowing you to make tests on .Net code, very useful also to refactor existing code!


Swagger :

A tools that helps you design, build, document, and consume your RESTful APIs.


Graph Explorer:

A tools helping you to create your graph requests


Don’t forget that you can find many sessions video in the resource section of the ESPC website: https://www.sharepointeurope.com/resource-centre/


Hope this helps !


Posted in SharePoint | Leave a comment

ESPC16 Feedback


Hello everyone,

As I told you in the previous post, the ESPC16 conference was full of information! Both for announcements made and for the tools used during the different sessions.

I will try to collect my notes on the various subjects to share them with you.

Some statements:

  • ContentTypeHub : there are a lot of features in SharePoint, and not all of them are good
  • Feature pack planned to be release every 3 or 6 month
  • Bulk download of files is planned
  • Add link as a document in document library is planned
  • Sooner or later save site as template will disappear
  • Upcoming SharePoint integration means you’ll be able to launch PowerApps directly from the SharePoint mobile app.
  • “It’s build on #SharePoint because I can ! ” Wrong reason!
  • “Data are more secured in the cloud than onprem !”
  • Power Apps : Only 500 requests by minute allowed by connection.
  • Stop using Appweb!

Technology to follow:

Another important point, Microsoft is listening to our experiences, so if you want to provide feedback , go to https://sharepoint.uservoice.com/

Enjoy your reading!


Posted in SharePoint | Leave a comment

Back on track

Hello everyone,

Wow, it’s been a long time since I said that! About a year and a half!


I had lost the passion to be part of the community but I was lucky enough to be able to take part in the European SharePoint Conference in Vienna this month and I confess I had a lot of fun chatting with the people there.


From the “simple” lambda to the expert / MVP / pnp member / etc .., everyone was motivated and passionate about what he / she did on SharePoint.


Seeing all this I tell myself that I will go back to publishing on SharePoint / Office 365, probably starting soon with a summary of the useful things I learned at this event.

Hopefully this will help you … again


Posted in Other | 2 Comments

Link in alert mail incorrect


Hello everyone,

Today I’ll talk about a problem with standard SharePoint alerts.

It can happen that the links in those emails use inaccessible url by end users, ie the URL of the server. This comes from bad information that can be found everywhere on the net, namely that the url is generated based on the URL used to specify the alert.

After making several tests on a SharePoint to date, I have always had the same urls little import the url used to set the alarm (perhaps a residual bug …)

The result of the tests is that the link used for alert messages is the link specified in the “Default Zone” of “alternate access mapping”.

So just change the order of URLs in AAM to have URL accessible by everyone in the default area.

Hope this helps,


Posted in SharePoint 2013 | Tagged , | Leave a comment