We use cookies to give you the best experience on our website. If you continue to browse, then you agree to our privacy policy and cookie policy. (Last updated on: November 16, 2018).
Unfortunately, activation email could not send to your email. Please try again.
Syncfusion Feedback

ODataV4Adaptor and property enableCaching

Thread ID:





120869 Oct 23,2015 11:55 AM UTC Oct 26,2015 12:55 PM UTC JavaScript 1
Tags: ejDataManager
Roberto Tonni
Asked On October 23, 2015 11:55 AM UTC

I need some clarification about the property EnableCaching.

Following what I would do:
  • A DataManager that uses ODataV4Adaptor to talk with my v4 OData endpoint (using ASP.NET Web API 2.2)
  • Enable caching to cache multiple page and to reduce multiple request to the server
I have therefore chosen to use the property EnableCaching.

In this way, however, the grid use the CacheAdaptor rather then the adaptor set in ejDataManager control.
This means that all calls to my OData endpoint v4 pass through CacheAdaptor, which produces OData incompatible requests (for example, an update request produces a POST instead of a PUT or PATCH); this means that it is called the wrong Web API action.

Is there a way to enable caching maintaining the original adaptor behavior?


Balaji Marimuthu [Syncfusion]
Replied On October 26, 2015 12:55 PM UTC

Hi Roberto, 

We considered this “CRUD operation support for DataCaching with odata Adaptor” as an usability feature and a support incident has been created under your account to track the status of this requirement. Please log on to our support website to check for further updates. 



Balaji Marimuthu


This post will be permanently deleted. Are you sure you want to continue?

Sorry, An error occured while processing your request. Please try again later.

Please sign in to access our forum

or the page will be automatically redirected to sign-in page in 10 seconds.

Warning Icon You are using an outdated version of Internet Explorer that may not display all features of this and other websites. Upgrade to Internet Explorer 8 or newer for a better experience.Close Icon