Hello,
We ran into an issue where the View Variants Module does not take different Data Access Modes into consideration between views. As the documentation states:
Each View Variant can have an individual IModelListView.DataAccessMode value (see List View Data Access Modes Overview), but this value is ignored. Instead, the value specified for the root varied View is used for all variants.
In most cases this makes sense, however, if the variant view's List Editor does not support the data access mode, the collection should be recreated using the new mode. Alternatively, before switching the view, a check should be done to ensure the new editor supports the root data mode and throw a friendly exception if it does not - and prevent the view from being changed.
In our scenario, we have a large list of calendar items that can be displayed in a GridListEditor with reasonable loading time in Server Mode. However, the variant for the SchedulerListEditor needs to load in Client Mode. When switching between these variants, an exception occurs and the user is stuck.
While we can do this ourselves with a controller, I'm making the suggestion to provide this capability out of the box.
Thanks!
-Dave
Thank you for contacting us regarding this scenario. We need additional time to research and discuss it. Please bear with us. We will update this ticket once we have any results.
We investigated how to manage this configuration better and will see how to improve our code, though I cannot promise any time frame. Nevertheless, thank you for your feedback. I greatly appreciate your cooperation.