xtrareport Entity Framework Filter

Hello Stephane,

Let me provide you with the information my colleague posted in the EFDataSource with Large Database and DataSource level filtering private ticket, where he discussed a similar behavior:

Thank you for your question. At present, the EFDataSource component doesn't support server-side filtering. That's something we look forward to as the XtraReport.FilterString expression always operates with the already loaded in-memory collection of objects, but right now, there are no time estimates. One of the possible workarounds here is to implement a stored procedure that would accept the required value as a parameter (it will be available only if defined in your EDMX model —  code-based modeling is not supported).  And if you don't have any stored procedures to bind to, here is an alternative solution: use the object binding approach. That is, use the ObjectDataSource component to expose the schema of the target class at design time (How to: Bind a Report to an Object Data Source). In this case, actual data should come from the XtraReport.DataSourceDemanded event (or its scripting counterpart) — this is where you're supposed to execute your LINQ query that will fetch data based on the actual report parameter values and assign the resulting IList collection to the report's data source. Just to be clear: the ObjectDataSource is not about the Entity Framework or any other ORM, it doesn't have any idea of what the DBContext is. Essentially, it's just a way to bind a report to an arbitrary class at design-time and expose its schema: How to: Bind a Report to a List Object at Design Time and Provide Data at Runtime.

In addition, take a look at the latest comment posted in the Report filter child report based on parent property thread.

Thanks,
Dmitry