The Baretta

On the 14th of May 2015, Yammer deployed an update to their Embed Yammer Feed script that stopped any Yammer Feeds on SharePoint 2010 from working.  In our case, the Yammer Feed got stuck on 'Loading...' This error that is causing the Yammer Feed to fail to load is: Object doesn't support property or method 'forEach' .  yam-platform-feed-57f4f449766511e4f91eb519a39b2781.js, line 480 character 19099 The reason this is happening is because SharePoint Master pages have a line of code which forces all Internet Explorer Browsers to run in IE8 Compatibility Mode.  This is done to ensure all the ribbon & SharePoint functionality continues to work on new browsers. The line of code in question:  <meta http-equiv="X-UA-Compatible" content="IE=8"/> Hint: don't just remove this line of code!  you'll cause yourself a headache. The line that Yammer & Microsoft are taking is that if you plan to stick to SharePoint 2010, th...

Most SharePoint customers suffer no issues when integrating SQL Server Reporting Services 2012 (SSRS 2012) with SharePoint 2010 (SP 2010), I however, had quite a bit of trouble.  So for those at home who may also be having some trouble, I thought I'd prescibe you some troubleshooting medicine along with a few spoonfuls of errors. The official steps you may have read about: - Install SQL Server with Reporting Services Add-in for SharePoint - Install SharePoint on the Reporting Services Server and connect that server up to the farm (using Configuration Wizard) - Install the rsSharePoint.msi file provided by Microsoft on all your front-end servers running SharePoint. - Run these two commands on all front-end servers running sharepoint Install-SPRSService Install-SPRSServiceProxy - Navigate to Central Administration > System Settings > Manage services on server.  Start the SQL Server Reporting Services Service - Navigate to Central Administration > Applic...

I feel like there are many sites/blogs/articles etc that list all the wondrous things that InfoPath can do.  They praise how user friendly it is for non-coders, how quick it is to design forms in comparison to Adobe & Visual Studio.  What none of them tell you is that if you want to design a code-less InfoPath form, you are severely restricted in many areas that you wouldn't realise, until of course you need to implement that functionality. "Why would you need to stick to a code-less InfoPath form?" you ask?  Well, in our organisation, the reason is simple.  We plan on creating many automated forms, and we plan on pushing them out to the various departments so that they can administer small changes themselves, only asking for help when they need technical advice. So as a coder who knows what can be achieved with a cheeky bit of C# here and there, I am going to list of issues I've found while trying to create a code-less form: ...