Limitations of SharePoint ListData.svc

The SharePoint RESTful API (ListData.svc) is a great and effective way to access data in SharePoint lists and document libraries for use in mobile/desktop web apps. However, you should be aware of some of the limitations of ListData.svc in SharePoint 2010.

  1. Anonymous access not allowed.

    Only authenticated users can use ListData.svc, even for lists that allow anonymous access. This means you can’t use ListData.svc in public sites.

  2. Property names based on display names instead of internal names

    In contrast to SharePoint Web Services and CSOM, which use internal names of the item fields, ListData.svc uses the display names (with whitespace trimmed). This can cause issues when your user changes the display names of columns or if your user can switch languages in a multilingual SharePoint site (the display names of fields may change).

  3. No access to External List

    You cannot access (read or write) data in SharePoint External Lists.

  4. No access to discussion list

    ListData returns HTTP 500 error when accessing a Discussion list. This is confirmed as a bug and has been escalated to the development team. More details here.

  5. Cannot use $filter beyond resource throttling threshold

    You cannot filter on a list with more items than the throttling threshold. ListData.svc does not take into account the use of folders. Full details in this blog post.

Did you encounter any other limitations? Let me know and I’ll update the post.


9 thoughts on “Limitations of SharePoint ListData.svc

  1. Pingback: Everything I need to know about RSS and XML Viewer Web Part (WP) « Automate IT!

  2. No ability to filter items created by “ME”, without specifying the correct User ID. With web-services and CAML you can use which automatically resolves to the currently logged in user. You can use _spPageContextInfo.userId to get the ID of the currently logged in user, but that won’t exist on a custom page without further trickery.

  3. #1 on this list should be “No managed metadata fields” in REST API, forces you to fall back on SPServices library.

    Also no indexing on standard “Name” field so filtering based on name on large lists results in an error: /_vti_bin/listdata.svc/Items?$filter=Name eq ‘Something’

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s