02 September 2014

Tag SharePoint Events With Time Reporting Data

TimeCard logotypeThe TimeCard for SharePoint documentation is almost finished, and today I can show one of the new demos: how to tag SharePoint events with TimeCard values.

TimeCard for SharePoint adds one, two or three dropdowns to each event in the TimeCard calendar. Here users may select tag values for each event, values that transforms the SharePoint event into a timesheet. The values only need to be defined once for all who have their TimeCard calendars in the same SharePoint site.
The TimeCard for SharePoint event tab

Report the events
As the events are transformed into timesheets, they can be used for time reporting directly from the calendar. Just click a button, review the data and make changes if needed before you report the time with another button click. Given permissions, users can also help each other to report time.

If the Expenses feature is enabled in TimeCard, the user's expenses for each event may be filled out in the event and reported with the hours. The default captions of the expenses form can be edited, so the TimeCard administrator may enter any suitable captions in the Global Settings for the site. Then these captions will be shown to all users and in the various Excel reports that TimeCard can generate, instead of the default ones.

TimeCard Demos
The demo above is intended for new TimeCard users. As you see it is very easy to tag the events, and the dropdowns minimize the risk for errors. The TimeCard for SharePoint Demonstrations page have three more demos for users. Personal Settings, Reporting and Statistics .

We have already sent the Beta version of TimeCard for SharePoint to some TimeCard Workgroup for Outlook subscribers, who were eager to test how TimeCard works on the new platform, and now we are looking forward to hearing their comments. Hopefully the next setup will be the release version!
Peter Kalmstrom
CEO and Systems Designer Business Solutions

28 August 2014

SharePoint 2013 Minimal Download Strategy and JavaScript

SharePoint logoToday I welcome our Lead Developer Jayant Rimza to the blog. He is often researching how to solve different problems that occur during the development process, and here he will share his solution to a common issue in development for SharePoint. The article is primarily intended for other developers: Jayant Rimza photo

SharePoint is growing rapidly, and Microsoft is putting lots of effort in making it faster, better and more user friendly. Minimal Download Strategy (MDS) and Client-Side Rendering (CSR) are big steps to achieve these goals.

Minimal Download Strategy (MDS) reduces data download on each page. When a user requests a page, only the changes are downloaded and not the whole page. It seems that SharePoint is soon going to be a single page application where all your content will load on a single master page.

You can identify MDS by these ugly looking URLs in SharePoint: "”.

It is possible to enable and disable MDS in SharePoint 2013. For more information on MDS and how to enable and disable it, refer to

Problems in JavaScript
JavaScript logo In SharePoint 2013 I have faced various problems with my old JavaScript code, that was running fine in SharePoint 2010. When MDS is enabled in SharePoint 2013, you will get errors like "object undefined", page load event code is not working etc. This is because the whole page is not loaded but only the required part, so page load events do not occur.

Garbage Collector
The major feature of MDS is that it also works as Garbage Collector for JavaScript. It removes all global “var” definitions from JavaScript, and you get an error: “Object undefined”. It also removes the definition of “var” like this:

var myobject = {
          Getname: function(){


The good thing is that MDS keeps all JavaScript functions. You will also notice that if you refresh the page all these errors will go away, because a page refresh is a full page load when everything is loaded.

Common solution
There are many suggestions available when you search on the internet, and most of them say you should use the “RegisterModuleInit” SharePoint function to register your module to load in MDS case. I hope it will help you, but I am not sure it does. It also requires condition and check if MDS is enabled or not.

My solutions
 I would suggest to instead create a universal code that will work on both cases, whether MDS is enabled or not. To take advantage of the fact that the SharePoint MDS does not remove functions but only clears variables, you can create self-executing functions or JQuery like a library. Here are two solutions for global JavaScipt object replacement:

  • JQuery Like JS Library
    This is a good way of writing your own JavaScipt files for shared and global code. JQuery like a library or self-executing functions are always loaded, and SharePoint will not give an “undefined” error. This method is good for big SharePoint applications and many JS files. From this example you can understand how to create such a library.

    (function () {
        // K returns new Library object
        var K = function () {
            return new Library();
        var Library = function () {
            this.version = '1.0.1';
            return this;
        // Extend the Library object.
        K.fn = Library.prototype =
            kSPErrorMode: {
                _errorStatus: false,
                get_ErrorStatus: function () {
                    return this._errorStatus;
                set_ErrorStatus: function (status) {
                    this._errorStatus = status;
                    //return this._errorStatus;
        if (!window.K) {
            window.K = K;

    To access object code like this: K().set_ErrorStatus(true);

    Now everything in your code is within a function. MDS will not remove things from your JavaScript, and your code will work well with both MDS enabled and MDS disabled sites.

  • Create Object when needed.
    You can create a function that returns an object of properties and a new object when you need it or new it when the object is undefined. This is good for simple or small applications.

    var Person = function () {
        var myObj = {};
        myObj. Name = "";
        myObj.Email = “”;
        myObj.IsAdmin = false;
        return myObj;

    var objPerson = new Person ();

    You can define objPerson globally and when accessing it, just checkif it is undefined or not.  If undefined, then create object:
    if (typeof (objPerson) === "undefined") {
            objPerson = new Person();
  • Take one more step and create a Closures function that will handle both check for object undefined and create objects. By the closures function you can write a whole logic of object undefined check and initialization in it and access properties:

    function MYBigObject() {   
       if (typeof (objPerson) === "undefined") {
           objPerson = new Person();
        return {
          MYPerson: function () {
                return objPerson;

    To access person object: 
    Var PersonaName = MYBigObject().MYPerson().Name;
    Like Person you can create many objects and make the return type in MyBigObject function.

Minimal Download Strategy (MDS) only loads changed content.
Minimal Download Strategy (MDS) works as a JavaScript Garbage Collector and removes all global vars.
To solve this issue, use the SharePoint “RegisterModuleInit” function, create a JavaScript like library or use create object instead of direct var.

This article has also been published in the Tips section.
Jayant Rimza
Lead Developer Business Solutions

26 August 2014

Manipulate The SharePoint Navigation

SharePoint logoIn my tutorial series on SharePoint Links I have now published the fourth article and demo. Here I describe various ways to manipulate the links in the SharePoint navigation areas Top Bar and Quick Launch.

SharePoint Server Publishing Infrastructure
How much you can customize your SharePoint navigation depends on a SharePoint feature called SharePoint Server Publishing Infrastructure. It is present in all SharePoint licenses except the Foundation versions, but even if it is there, SharePoint Site collection features it has to be enabled for each site collection.

If you have a license with the Publishing Infrastructure and it is enabled, you will get more customization options. But also without them, there are some possibilities to make changes in the SharePoint navigation. In the Tips article on how to manipulate the SharePoint navigation you can find a list of the options I show.

Manipulation and Solutions
When you are using a SharePoint Solution we recommend you to not manipulate the Quick Launch on the users interface of that product. It is possible, but in general it is better to have several SharePoint subsites instead of cramping many different things in one page.Kanban Task Manager for SharePoint logotype

The Top Bar is often a global navigation for the whole site collection, and you can manipulate it as you like when you use a SharePoint Solution. It is convenient to be able to reach all other sites in the collection from the Top Bar in your Kanban Task Manager or TimeCard page. TimeCard logotype

Top Bar dropdowns
Even if I recommend the use of subsites, I am aware of the drawback: when you have many sites in a site collection there will be a long row of links in the Top Bar. This can be avoided if you have the Publishing Infrastructure. Then you may use dropdowns for the Top Bar navigation. They are not difficult to create, and in the end of the demo below I show how to do it.

All the SharePoint Links tutorials are gathered under their own heading in the table of contents of the Tips section. You can find many other articles there too, on SharePoint as well as on other platforms. You are very welcome to browse!

Peter Kalmstrom
CEO and Systems Designer Business Solutions