The DataSource documentation for canSyncCache states that "if canSyncCache has been set false, the server will skip the cacheSyncOperation" but this is not the case. It appears the setting canSyncCache="false" has no effect, but setting invalidateCache="true" does.
Announcement
Collapse
No announcement yet.
X
-
Actually, the documentation is correct - that is the intended behavior, but it turns out that we were only honoring canSyncCache:true. This is the more interesting case, of course, as this is the setting that allows you to tell the framework to override the normal rules, but an explicit false setting should also be honored as documented. We've fixed this now in 3.1d and 3.0p.
Thanks for the problem report.
Comment