Skip to main content


Thoughts, shortcomings, gotchas on SPFx Dynamic Data capabilities

It's the festive break, and I thought I'd try the new Dynamic Data capabilities that recently went to General Availability in SharePoint Framework 1.7. I've been building a lot of React components lately, and all the SPFx web parts and application customisers with visual elements we create at Engage Squared, are built on React.  Dynamic Data in SPFx introduces a whole new world of modularity that we haven't had before. We can now split up the page elements into multiple web parts that, in the past, have been combined as one web part so state can be passed between them.  Doing this gives control back to the page author, with the ability to position components how they wish. Breaking components up in to individual web parts also changes the way the components are designed, and forces the developer to leverage the responsive capabilities of modern pages.  Modern pages are designed from the ground up to work on many different screen sizes, and as long as each individual
Recent posts

Apps for SharePoint 2013 - Client and Server-side code

It's about time I blew the dust off this blog. Tonight I did a presentation at the Melbourne SharePoint User Group entitled Apps For SharePoint (2013). It included two demos based on the App For SharePoint 2013 solution template in Visual Studio 2012. The two demos illustrated how you can create a separate ASP.Net Web Application. Demo 1 showed how easy it is to hook in to SharePoint to obtain List properties via server-side code (populating an ASP.Net Repeater Control). Demo 2 showed what you can do with SharePoint 2013's Javascript hooks. Specifically, using SP.UI.Controls.js from the /_layouts/15/ SharePoint folder to pull chrome elements out of SharePoint, and render them in your ASP.Net web app. No animals were harmed in the making of these demos, but a few articles kindly provided on the Microsoft MSDN site helped put it together: How to: Set up an on-premises development environment for apps for SharePoint How to: Create high-trust apps for SharePoint 2013 usin

SharePoint 2010 Content Migration - PDF icons don't appear in document libraries

Description When a document library includes PDF files, by default these file’s icons are displayed with the generic “blank” icon. Resolution Upload the .gif file for the PDF icon to C:\Program Files\Common Files\Microsoft Shared\Web server extensions\14\Template\Images Update the Docicon.xml file in the following folder C:\Program Files\Common Files\Microsoft Shared\Web server extensions\14\Template\Xml\ to include the following node: <Mapping Key="pdf" Value="NameofIconFile.gif"/> Restart IIS after making the change Details on how to perform this for all versions of SharePoint are available at this Microsoft KnowledgeBase article .

SharePoint 2010 Content Migration - Custom Content Query Web Part doesn’t show some Lookup data from underlying list

Description Fields used in a custom CQWP that are of "Lookup" type don’t render out correctly. This occurs when the CQWP is designed to strip extraneous information from the values of the Lookup field Resolution Updates to the custom CQWP .webpart file, and the associated XSLT file are required. Ensure the .webpart file refers to the Lookup field as a “Lookup” type in the CommonViewFields node, and update the XSL file associated to the CQWP to no longer remove characters prior to a “#” character (SharePoint 2010’s CQWP parses the data from a Lookup field without the pure “2;#Value” style rendering, instead the looked up value comes out in the CQWP as “Value”)

SharePoint 2010 Content Migration - Discussion Boards web parts don’t function

Description Discussion Board web parts that exist on pages throughout the site don’t work. When you select a link to view a Discussion Board thread, the link doesn’t send you to the thread details. Instead it sends you back to the same page, but the Discussion Board web part is emptied Resolution Ensure SharePoint Server 2010 SP1 and the SharePoint Server 2010 June 2011 Cumulative Update is installed prior to performing the db attach upgrade.

SharePoint 2010 Content Migration - Broken images on Contact Details web part

Description If you're migrating some content from your MOSS 2007 environment, but staff photos are remaining at their original location, profile data included in content (i.e. in Contact Details Web Parts) may include source addresses that are updated via the database-attach approach to refer to the new 2010 site collection’s host name. Resolution Possible resolution is to ensure a profile sync is done from Active Directory and subsequently perform profile sync to site collections (run the respective Timer Jobs), after the site collection is migrated