Our client recently decided to upgrade from SharePoint 2007 to 2010.
I was tasked with determining what modifications, if any, would need to be made to our custom site template.
This is the story of my trials and travails in doing so…
With the SharePoint Conference 2012 behind us, I have been reflecting on our SharePoint journey so far…and on the road ahead. And what an incredible journey it has been! SharePoint has allowed AIS to build mission-critical applications for various large federal government agencies and commercial organizations. And not just ECM or document management systems (which are great workloads enabled by SharePoint) but enterprise-class applications for tens of thousands users (such as the FBI’s Delta Project), built using SharePoint platform elements such as workflows, lists, libraries, search, etc.
This blog entry is comprised of two parts. The first part will focus on the SharePoint journey so far. Through a series of short video clips, I will present some of the key insights we have derived over the many years of building custom applications on SharePoint. We will end this the first part with a short demonstration of SharePoint-based Case Management application that brings together many of the key concepts. The second part will focus on the road ahead and the most important enhancements made in SharePoint 2013. Read More…
Microsoft Dynamics CRM 2011 has come a long way from its predecessors in many areas. For companies using both CRM 2011 and SharePoint 2010, the improvements can be appreciated even more since Dynamics CRM 2011 has native SharePoint 2010 document management capabilities right out of the box.
This functionality is apparent in a couple of different places in the CRM 2011 web interface. First, there is a page under the Settings section for Document Management. Second, some entities will have a Documents area available on their forms. Please see the screen shot in Figure 1 below. (Click on any image to see full-size.)
For this write-up, I’ll be focusing on the Document Management page and the required steps for configuring access to SharePoint 2010 as well as installing the SharePoint List Component.
This week, many AIS team members are attending the Microsoft SharePoint Conference in Las Vegas, Nevada. We’ll be posting blog posts from each of them as they learn what’s new and what’s exciting during sessions, demonstrations and other conference highlights.
During yesterday’s breakout sessions, I attended Sean Livingston’s session on SharePoint 2013 Upgrade. A few minutes into the presentation, Sean offered up a quip that is certainly true across any platform level migration: “Upgrades lead to unpleasant feelings between the users and the IT staff.”
To be fair, upgrades bring “new stuff,” which often the users are clamoring for. However the process of designing, engineering, implementing and provisioning the upgrade tends to be long running, particularly where large blocks of content must be migrated from one version to another. Upgrade plans must carefully balance the run times required to upgrade the content, training time for users and other background tasks against the need to keep serving up content through the transition. Migrations can be a headache from start to finish. However, several features in SharePoint 2013 aim to ease the upgrade process, if not completely avoid all headaches.