Adding page specific yammer feed


So, a lot more projects I’m working on involves yammer, whether its being the entire feed, a count of notifications or page specific feeds.

Page Specific code can be found Here

The code I’ve included is fairly simple but adding this into a page layout will let you have a feed on each page created from the layout which will be personal to that page. Adding in the “defaultGroupId” to the config will allow you to have the feed default to a specific Yammer group, this can be useful for news if you want a specific news yammer group.

To get the GroupId, open up the group on yammer, in the url of the page you should have a number at the end and this is what you will need to add into the config.

config: { defaultGroupId: 3257958} });

Hope this helps!

Notes from Ignite 2015 – SharePoint 2016

SharePoint 2016

SharePoint 2016

This is a list of things that I’ve picked up from the Microsoft Ignite 2015 event from either watching videos of the event or reading articles from those there.

  • You can only upgrade to 2016 from 2013, 2010 instances will have to upgrade to 2013 first.
  • Less focus on windows authentication and more Saml and OAuth are being pushed forward.
  • Extranet scenario – Publish internal sites to internet. I’m unsure how this is going to work, I thought Microsoft were dropping public facing SharePoint sites, Possibly for only on-prem.
  • Upon installing SharePoint you can assign it a role, The wizard will run a health check on the server to check it is capable of running the role. Roles seen so far:
    • Special Load
    • Web Front End
    • Search
    • Application
    • Distributed Cache
    • Single Server Farm
  • The next-generation SharePoint product will reduce the number of restarts by reducing the overall number of fixes contained in the patch itself
  • User profile service application will be removed, AD import will still exist but the profile sync will be removed. If a client wants the User Profile service, Forefront Identity Manager will need to be set up as a separate server outside the farm.
  • Content DBs in the Terabytes, 100,000 site collections per content DB. The list threshold will be greater than 5000, the max file size has been increased to 10 GB and character limit restrictions have been removed and index items are increased to 500 million items. Some numbers are still to be announced from Microsoft.
  • Fast site collection creation – New logic: copies site collection at content database level; so there will be a “master” site collection; features don’t have to be activated, as the features are already activated in the “master” site collection
  • Project Server – More features and now more integrated with SharePoint;
  • Durable links – Id based URL’s that don’t change even when the content moves to another site or site collection.  Users can email links to content and not worry about a broken link if the content moves.
  • Real time analytics – Since Power BI really took off on 2013 for SharePoint it looks like they’re expanding on this, we can expect decent dashboards for usage analytics, info about things like latency, which docs are accessed more than others, daily active users, storage, storage by site template, daily storage, etc.

SharePoint 2016 has some interesting features coming up, I’m looking forward to working with the new analytics on 2016.

Simple REST for SharePoint

There are many ways of getting the data from SharePoint to use in web parts, the first approach I ever took to creating a web part was to use the ListData.svc. With JavaScript I was able to grab data I needed to create a web part that produced a set of links (My first web part was slightly boring). If you enter the service into your browser, it will give you the lists you have access to.
Then find the list you are wanting to draw your data from and put it at the end of your url.
Of course your site and list name will be different from the ones I’ve used as an example but in this instance it would return the data on the items in the FavouriteBooks list. Using this you can then run code against the data to pull out what you are trying to fetch.
This is a very simple rest call, if you set the SiteName to “” it will then run this code against the root of your site.
var SiteName = //Name of your SP site
var ListName = //Name of your SP list
$.getJSON(SiteName +  “/_vti_bin/ListData.svc/” + ListName, function (data) {
        $(data.d.results).each(function (index, value) {
The above JavaScript will return the title and description of each item from within your list, it doesnt do anything with it but if you were to have a breakpoint next to the returned values and then type them into the console, you would see the value returned.

SharePoint Publishing Site

SharePoint Publishing sites are probably my favorite of the OOB Site Templates. With all the standard features you get from SharePoint you get a whole lot more structure to your site.

Publishing Feature

The biggest part of the Publishing Site is the “SharePoint Server Publishing Infrastructure” which enables you to check files out while you edit them. Once you have checked a file in, your changes will only remain visible to those who have access (depending on how your security groups have been set up). Publishing the page will then set the page for everyone to see the latest version.

If your site has approval workflow activated then the published document/page will need to have approval from selected users before it is fully published to all users.

Master Page and Page Layout

SharePoint Publishing Feature allows the site to create, edit and delete your own master pages and page layouts for your site, this can be useful if a your site wants different branding from the parent site or if you want to create page layouts that include site exclusive web parts.

Content Query Web Part

The Content Query Web Part in my eyes is one of the most useful tools in the SharePoint Web Part arsenal. This allows you to query against sites or lists for information. You then specify the items you’re looking for by their content type and start filtering/sorting/grouping your data by further queries against the results. Within your site Style Library you can download the “.XSL” files for the content query and modify them to customise your output on the page.

SharePoint Project site

Project site templates have been designed with tight team work in mind. If you are part of a team and require a site for planning out work, this site template will be ideal for you.

Task List

A task list is predefined by SharePoint which allows you to instantly set up tasks within your site. With this you can assign team members to tasks  and have an email notification sent to them letting them know!


An OOB function of the Project site is the timeline, the timeline lets you put your tasks into a visual guide that helps project management. For those familiar with Microsoft Project, you will be familiar with a lot of the functionality including task dependencies and sub tasks.

Microsoft Project

If you prefer to keep to your local applications or work on the go with limited internet access you can Use Project with SharePoint. An advantage of this is project plan access to those working in industries not office based is being able to take your information anywhere.


Document collaboration is a great feature within SharePoint that allows team members to work together on documents, the Project Site allows you to do this out the box. Adding a lookup field to the task list, you can have documents assigned to tasks.


After your project site is set up and you have started using it, you may decide you want to share your project information with others, you may want to only show some information of the project to the client, the Project Summary Web Part will help you in achieving this.