Use SqlDataSource SelectCommand xml element instead xml attribute

Progress® Telerik® Reporting Feedback Portal

Create an account Log In

Back to Feed

Request a Feature Report a Bug

Need More Info

Last Updated: 17 Oct 2025 10:30 by ADMIN

Sergii

Created on: 02 Oct 2025 13:32

Category: Reporting

Type: Feature Request

Use SqlDataSource SelectCommand xml element instead xml attribute

Use SqlDataSource SelectCommand xml element instead xml attribute - it allows to write complex sql requests in any tool and just put it into xml without changes and have it well-formatted and readable:

So, instead of

save it as

or even

3 comments

ADMIN

Todor

Posted on: 17 Oct 2025 10:30

Hi Sergii,

Thank you for clarifying the requirement.

I have approved the request. We will consider it for future releases, depending on the support from our community, among other factors.

Regards,
Todor
Progress Telerik

Your perspective matters! Join other professionals in the State of Designer-Developer Collaboration 2025: Workflows, Trends and AI survey to share how AI and new workflows are impacting collaboration, and be among the first to see the key findings.
Start the 2025 Survey

Sergii

Posted on: 10 Oct 2025 18:05

Hi Todor,

for me it is first of all it is reading xml as plain text wit tools like notepad, WYSIWYG for multiline sql text which would be copy-pasted from MS SQL Mangement Studio (where it can be debugged) to designer and vise-versa.

Second is versioning purposes, when changes in sql can be tracked as example git and would be readable and analyzable without checking out specific commit, run report designer, etc. - inside versioning tool gui/frontend

best regards,

Sergii

ADMIN

Todor

Posted on: 09 Oct 2025 10:25

Hello Sergii,

Thank you for sharing your requirement.

Based on the screenshot, it seems like you would like the query to be better formatted in the XML of the report definition. Why do you need this?

Would you like to read the report XML with an external tool or custom code? If so, this is not the purpose of Telerik Report definitions. They are meant to be read by the Telerik Reporting functionality.

Or do you want to change the XML definitions outside of Telerik Reporting functionality? Note that this may lead to failures when upgrading to future versions. Generally, we may change the way we handle report definition, or its format, and this would be reflected in a newer XML schema. The external modifications may not comply with the introduced reporting changes and make the report definition invalid.

We would appreciate it if you shared more about the scenario that requires this feature.

Regards,
Todor
Progress Telerik