I have a webservice which provides me with tabular data, which I would like to display in SharePoint in the typical SharePoint-List way. Now I could simple copy the html and styles and build the tables and context-menus etc. from scratch, but I'm hoping that there's some (well)hidden feature of javascript OM which will make this easier for me.

Is this possible? Does anyone have pointers or examples for this approach?

P.S. I don't want to do this server side. That would be too easy :)

Update: I'm trying to integrate an existing LOB Application into SharePoint. this application offers a restful webservice API. The Main reason I want to use the Client Side OM IS ease of Development, deployment and Maintenance. As the existing App is a product which will be installed in many different Client Szenarios, having a Solution which has very little impact on the Infrastructure is a big plus.

  • I'd suggest that you include a description of your motives for doing this as it might be easier to suggest some other possibilities for you rather than just BCS or COM. Sometimes when we have a problem we focus on one way of solving it that is not optimal and if a third party understand why we are trying to do something they can suggest a better way that we were unable to see because we have focused on one way of solving the problem. Mar 12, 2012 at 18:09
  • Updated motivation
    – AyKarsi
    Mar 13, 2012 at 6:18
  • This isn't really a COM question. Really it just comes down to skinning and using JavaScript (JQuery or some other library would ease development) and using the SharePoint CSS to style it the way you want. The JavaScript would get the data and then you would use the proper CSS to display the controls and HTML it produced in the way you want. Mar 13, 2012 at 12:47
  • that's what I meant "with copying the html and styles and building it from scratch.." I was hoping there'd be some OM objects and methods which would make it building the tables a lot easier..
    – AyKarsi
    Mar 13, 2012 at 13:28
  • That's not really the purpose of the client object model, though. COM is about performing CRUD operations on SharePoint objects and data. There may be a JavaScript library for simplifying the creation of HTML, but the COM is not it. Mar 13, 2012 at 13:48

3 Answers 3


If coding is an option, take a look at the SPGridView. I think you could achieve what you want with a sandboxed solution.

Going the client only route is feasable, but difficult, as SharePoint generates a boatload of markup, styles and scripts to get everything working.


The simplest way is to create BDC. Then you can create external list. It works and looks like sharepoint list, but have several limitations.

  • I only have SharePoint Foundation to work with, and using BDC is to much configurative hassle anyway.
    – AyKarsi
    Mar 12, 2012 at 16:06
  • BCS is included in SharePoint Foundation and it's not that much trouble to configure. It is certainly less difficult to configure than writing anything but the least trivial JavaScript for the COM. Mar 12, 2012 at 18:05

I know you won't like this, but if you cannot use SPGridView, look at JQuery Template. This would help you more easily create the UI.


Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.