Ever wanted item level security in SharePoint without the headaches? It’s easier than you might think.
If implementing SharePoint with another ECM solution, it is important to truly identify what role SharePoint will have in the organization to ensure proper planning for the implementation.
I don’t think I’ve worked with any client that was happy with the SharePoint look out of the box, generally that means a “make it look not like SharePoint”
You already knew this, but strong user preferences for SharePoint sites translate into value in many ways.
The value of SharePoint is often best broken down and contextualized by organization, division and department.
I don’t think I’ve worked with any client that was happy with the SharePoint look out of the box, generally that means a “make it look not like SharePoint”
We needed a SharePoint Dashboard that the end user could select filter criteria once and it would be pushed to all pivot tables on multiple sheets within one workbook
I gave a presentation to the New York Smalltalk User Group at which
Again, my aim wasn’t to list every possible reason a SharePoint shop would want to upgrade from 2007 to 2010, but simply wet your whistle with an overview of SharePoint 2010’s superior feature set. I highly encourage any organization currently invested in SharePoint 2007 to start considering SharePoint 2010 specifically in respect to their organizations current pain points with 2007. What they will find is that 2010 will address those points nearly line for line.
The hype cycle has started for the upcoming release of SharePoint 2010 and I’m certainly not the only one to get caught up in it




