I’ve ceased using the “Out of the Box” forms. I don’t even use the WebParts unless I have to.

To me the most useful part of SharePoint is the REST API.


I organize my sites into little armies of lists and document libraries that hopefully the user will never see.

My user will experience the site the way I want them to. I force them into custom home pages and dashboards cultivated with bootstrapped themes. The data pulled via SharePoint services into widgets and forms and charts that dance merrily beneath their cursors.

Microsoft all but abandoned Chart web parts in 2013. The ones you can make with Excel services are clunky and static. So I pull my data from REST and push it into FusionCharts or GoogleCharts or YahooCharts.

You could still use the OOB list view for some things and hack the DOM to spruce up the rendered layout… or you can consume that List into a JSON object and use Angular to bind it to a view with sorting capability.


For me it comes down to least amount of time involved… not just for set up, but for maintenance. If I know I’m going to be asked to group rows and columns, or add totals in a manner that isn’t possible with the OOB view, it’s worth it to set up the Single Page App to do it for you.

Categories: SharePoint

Related Posts


JavaScript SharePoint People Picker

Yes.. JavaScript SharePoint People Picker… try saying that 3 times fast. Anyway, I needed one for a form I was developing. It had to be client side, and it needed to work with SharePoint. In Read more…


A tragic tale of mutliple lists and forms and IE9

I’ve been busy on a project for SharePoint. This particular environment is unique in that the developers do not have access to the farm, and must put any requests through a processed managed by the Read more…


List Creation Naming Best Practice

When you create a new List or Document Library or “App” object in SharePoint, the name of Object is the new URL – in essence what we WordPress users would call the “slug” or permalink. This is a Read more…