I would like for there to be a feature in the report designers, where when I use the SqlDataSource component, the designer automatically picks up what fields I am using in the report, and edits the SQL query's SELECT statement to include only those fields.

To clarify our usage scenario: we design reports directly against SQL tables, stored procedures, or views from the start. The report definition is dynamic and often driven by user input, so we rely heavily on runtime evaluation. In our current reporting system, the optimization happens automatically during execution: The engine inspects the report layout and selection formulas, then generates SQL that includes only the fields actually used. This means the designer doesn’t need to manually prune unused fields — the runtime engine handles it intelligently.

In Telerik Reporting, we envision a similar behavior: once the report definition is finalized (whether in the designer or programmatically), the engine could analyze which fields are referenced in expressions, filters, groupings, visibility conditions, etc., and optimize the data retrieval accordingly. This would be especially beneficial for stored procedures or views with wide schemas, where only a subset of fields are relevant to the report logic.