Another complaint about CSV Header Format

[REI Software]

I've read through multiple posts complaining about CSV format, but here I am regardless. The CSV exporting function does not properly export the headers of my list.

If I export the report as a PDF or any other format I'll get the header to say "Timestamp".

As a CSV file, it will say "timeStampDataTextBox" Which is obviously not what I, or ANYONE, would want.

I don't care if it is a human readable format or not, the data represented in that field is "Timestamp" not a text box. I still need the headers in my export, so turning them off completely is not useful. What I need, is to be able to format the header's text so that is appropriate.

How come by labelsGroupHeader text box values are not even displayed? How come you decide to instead use the text boxes programmatic name of the fields values instead?

From what I've seen the standard response to complaints regarding the uselessness of CSV export is met with responses claiming that they are doing it wrong and don't address the real problems people are having.

[REI Software]

Hmm well I as able to get the basic format corrected by 

<Telerik.Reporting>
        <Extensions>
            <Render>
                <Extension name="CSV">
                    <Parameters>
                        <!--<Parameter name="NoHeader"
                                             value="true"/>-->
                        <Parameter name="NoStaticText"
                                             value="true"/>
                    </Parameters>
                </Extension>
            </Render>
        </Extensions>
    </Telerik.Reporting>

and then programmatically setting each of my TextBox's Name properties after InitializeComponent. I'm still not extremely happy about it though. I dunno

I guess I don't see how any CSV import would be helped by having the header repeated in the previous columns over-and-over. And also, why the top headers weren't the actual headers to begin with, but instead the field values code names.

[Steve]

Hi Alan,

The behavior you have observed is by design and noted in the Design Considerations for CSV Rendering help article. It represents our view on the export to csv and is not pushed due to some technical limitation or requirement, moreover it could be changed as you have found out already.

Kind regards,
Steve
the Telerik team