Tell me more ×
SharePoint Stack Exchange is a question and answer site for SharePoint enthusiasts. It's 100% free, no registration required.

I have custom list filter web part for SharePoint 2010 lists which I am trying to migrate to SP 2013. It works by modifying the list's XML definition and replacing the query with one the user created (via custom UI elements).

Yes, it's true that list filtering has been greatly improved in SP 2013, but it still is not able to filter on ranges (greater than, less than, between), so I need to port the custom list filter from SP 2010 to SP 2013.

My problem is that when modifying the XML definition of the SP 2013 list, the whole thing gets screwed up. The data in the rows gets replaced by lots of errors.

After some investigating, I've found that the new SP 2013 lists use "Data View Caching" as an option. If you disable this option the list loses all the new features and reverts back to looking like an SP 2010 list. I assume this means that the list expects the query on the server side to be unmolested and that all filtering happens client-side.

Has anyone figured out yet how to pass custom client-side CAML queries to the new SP 2013 list? I assume this will be the only way of doing custom filtering on it.

Thanks.

share|improve this question

Know someone who can answer? Share a link to this question via email, Google+, Twitter, or Facebook.

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Browse other questions tagged or ask your own question.