Performance - Implement a CollectionSource based on a data view (e.g., XPView, IDataRecord) rather than on a collection of persistent objects

Can you describe its use in 14.1 a little bit so we can plan a little bit? :)

@Nate: The Options node in Model Editor now provides the DataAccessMode property instead of the UseServerMode one. Possible values are Client, Server and DataView. ListView in DataView mode operates as if it uses XPView or EfDataView internally instead of XPCollection (I briefly touched this at the end of this blog post). We will provide more information on this feature closer to the release. Please stay tuned.

That sounds great. Will we be able to benefit in Dashboards and the Scheduler?

Yes, this is a feature of any ListView (even if it is used inside a dashboard). As I mentioned above, it will be more appropriate to discuss the feature implementation details and limitations close to the release time when more info is publicly available in blogs, docs, demos, etc. Thanks for your understanding.

Hi Dennis, can you tell me if the 14.1 release is scheduled for May?

Yes, late May.

Nate, I have added more details to our initial answer.

Thanks Konstantin. That sounds great. Where do you define the members of the XPView? In the model or in code, or both?

Looks good. Will this feature or an equivalent also be available for reports and analysis (where IMO it is most needed)?

Thanks for your interest.
@Nate: By default it is configured based on the information of the ListView node in the application model. More information and tutorials on this will be available after the final release.
@Jascha: The new ReportsV2 already provides a similar ViewDataSource component. As for the PivotChart module, it does not currently use the new data view mode.

Wow! It just pulls in the columns as whatever we have defined in the list view??? :-O That's pretty awesome and a very good implementation. I can't wait to get my hands on 14.1!

Does the ListView Support all Features? (Conditional Formating and so on…)

When the 14.1 beta version will be available for your loyal customers ? can't wait:)

@Nate: Yes, except for columns corresponding to non-persistent and reference properties. For the latter to work, it is required to add a custom model column pointing to a nested property, e.g., Department.Title.

@Noxe: ConditionalAppearance is not currently supported, but it is certainly on our radar. It is likely that it may be added in one of the next iterations, but I cannot promise any time frame at this time.

@Gustavo: You will automatically be notified via email once it is available for testing.

@Noxe: ConditionalAppearance is now supported for ListViews operating in DataView mode.

@All: The described functionality will be out as Beta in 14.1 and will basically work for Grid List Editors in the first version. The remaining built-in ListEditors (like TreeList , PivotGrid, Chart, Scheduler, etc.) will operate in Client mode by default, even if the DataView is specified in model settings. Support for these editors is planned for the future. There are also some specifics on the Web, which we also plan to overcome in the next versions. For instance, to enable this functionality on the Web, modify the Global.asax.xx file as shown below:

C#
protected void Application_Start(Object sender, EventArgs e) {  
     ASPxGridListEditor.OldColumnsCreationMode = false;  
}  

All in all, we look forward to receiving your feedback on how this works for Grid List Editors.

Great! Thx Dennis! (i guess an beta release will come soon? ;) )

@Noxe: Welcome!
Yes, it is around the corner. As always, you will be automatically notified when it is available.

What's 'future' mean for Scheduler/Charts? 14.1.5, or 16.2? That was what I was most excited about?

@Nate: I do not have answer to your question at this time, as I forgot my crystal ball at home:-), but we hear you, and I really appreciate your interest in this cool functionality.

Note that I have updated our original answer with instructions on how to choose an appropriate data access mode.