Softlanding: SharePoint Consulting & Managed Services | Vancouver, BC

    Enhancing Enterprise Productivity Since 2000

    Softlanding helps organizations be their best by providing technology solutions and services that make them more productive. Softlanding specializes in Microsoft enterprise technology platforms, leveraging a combination of cloud, on-premises and hybrid configurations to increase productivity from the data center on out to end business users. Platform specialties include SharePoint, Azure, Office 365, Power BI, Enterprise Mobility Suite and System Center.


     SharePointROI Sustainment Services

                                                           SharePointROI is a, fixed- fee managed service providing end-to-end SharePoint sustainment, user support and adoption services. Eliminate SharePoint expertise hiring headaches and get the most out of your SharePoint investment.​

    Learn More >>

     Current Openings

    Looking for a career? We're on the lookout for fun, talented people to join our growing teams. If you're looking to progess your career, apply here:

    Openings >>



    Takes Place:
    Description: Microsoft Canada opens its datacentres to Canadian businesses. Learn how Softlanding and Microsoft are working together to deliver the cloud Canada-wide.

     Featured Solutions

    Connecting Talent and Resources for Better Performance

    Corix finds a scalable solution to communication issues and improves organizational performance in the process. Read more here


     Hidden Title

    Strategic IT to Support Organizational Change

    The BC First Nations Health Authority finds a strategic partner for a major transition, plus continued IT support for successful delivery of essential services. Read more here​. 



    Posted on:
    Categories: SharePoint;Office 365
    Description: At Softlanding we strongly follow the cliché but important motto "practice what you preach". It's simple, until you have truly used something in your day-to-day work environment, you won't be able to know its behaviour in "real life" scenarios.
    ​At Softlanding we strongly follow the cliché but important motto "practice what you preach". It's simple, until you have truly used something in your day-to-day work environment, you won't be able to know its behaviour in "real life" scenarios. At Softlanding within the applications group, we have regularly scheduled meetings called Creativity and Inspiration Conversations (CIC) to discuss emerging technologies, features, practices or generally a "cool" solution we might have come across. These are informal discussions rather than rigid meetings, which are intended to promote thinking outside of the box and sharing ideas. In the past we have supported this discussion by simply setting up a recurring calendar invite. Typically before the meeting we assign someone to generate a topic and maybe review the topic with members prior to the meeting. Again this is intended to be informal and more of a conversation starter, so when I heard of Office Groups, it just seemed like a natural fit to support our CIC use case. It was simple, I created a new public Office Group, added the application team as members of the group. Then with the shared calendar feature of Office Groups I created a recurring meeting and invited the members. The members were notified that they had been added to the new Office Group, and automatically they were able to see the Groups calendar events overlaid on their calendar in outlook. Next I started a new conversation in the Office Group, where I had control of notifying individual members or the entire group of the potential topics for the next CIC session. We were able to host discussions within the group conversation area, without having a dreaded mass email chain. Any supporting files for the meeting are stored in the Files area of the Group. This cuts down having to email things like screenshots back and forth or creating a formal team site to store temporary documents. The Good Groups are easy and quick to set up, which really makes sharing content with others more natural The calendar within the Group is really a core functionality, being notified for meetings and seeing Group meetings overlaid on your own calendar makes it hard to convenient and centralized Office Groups provide a great way of potentially cutting down on email discussions, by providing a dedicated place to have conversations and be notified when you have been mentioned Rather than adding individuals as members to your group, if you add an Active Directory group, it will detect the users within the group and add them for you The Bad There seemed to be a lag time between the web app and installed client version of Outlook when updating events in Groups. It took between 30 minutes to one hour to reflect event updates between both versions of Outlook, which I can see frustrating many users Additionally, there also seemed to be a long waiting period before members were notified that they had been added to a Group The Great There is a dedicated Office Groups app also available for Windows, Android and IOS There is now integration between Microsoft Planner and Office Groups, you automatically have a plan created per Group where you can start tracking and assigning tasks It was also announced that there will be integration between Groups and team sites. This is for more complex scenarios where you want to have the power of using team sites and the versatility of Groups' scheduling and discussions

    Posted on:
    Categories: SharePoint
    Description: How to enable IntelliSense in Visual Studio for SharePoint-addin project type
    ​Let me start this post with a statement I'm a developer and developers love IntelliSense. If you are a developer too, you know what I'm talking about! Recently, I created a SharePoint-hosted add-in in Visual Studio 2013. While starting to code, I recognized that IntelliSense wasn't working correctly. Here is an example I tried to create a new ClientContext, but as you can see, IntelliSense is not providing the proper functions nor properties In fact, all the JSOM functions and properties were missing, which makes coding a SharePoint-hosted add-in needlessly difficult. IntelliSense is a very helpful feature, and I refused to continue coding without proper IntelliSense. So I started some investigation to see why IntelliSense wasn't able to show the JSOM stuff. First, I checked the _references file which is usually located in the project's Scripts folder. This file was existing, and its content looked correct. In a nutshell, this file is referencing the SharePoint JSOM libraries and the files listed here are supposed to be added to the IntelliSense database – but for some reason, this isn't working for my current project. My next step was to check if the _references file is actually used by Visual Studio to feed the IntelliSense database. To check this, I opened <Tools> <Options> in Visual Studio. In the text box at the top, I typed in 'JavaScript' and the following dialog is shown I clicked on References just below IntelliSense to see which libraries were included to build the IntelliSense database. The file _references.js was included just like some other libraries. Although _references file was listed here, it was not used to update the IntelliSense database. The basic configuration looked ok, and so I was looking for a workaround to get IntelliSense to show the functions and properties of the JSOM objects. I manually downloaded the file SP.runtime.js from SharePoint and added it to the Scripts section of my Visual Studio project. Because I did not want this file to be re-deployed back to SharePoint each time the app gets deployed to SharePoint, I changed the Deployment Type of this file to NoDeployment and I repeated this with the file SP.js. Time for a new test - and this time IntelliSense was working as expected! Now the IntelliSense database has been updated properly and was able to show all functions and properties which are part of the JSOM libraries – and this makes coding with JSOM a lot easier! It looked like Visual Studio wasn't able to access the referenced files which are listed in _references.js. Adding them as downloaded copies to the Scripts folder in my Visual Studio project enables IntelliSense to access them and update its internal database. As long as those files are kept locally and are not deployed back to SharePoint, this workaround can be used to fix the initial IntelliSense problem. But keep in mind as those files are local copies now, they won't get updated automatically!