G'day All,
I've got a very basic report which has two data bands with a table on each. Each table has 15 columns and one row. The first table is intended to be a header for the other table.
When I preview this report in Designer, it's ugly but it works - there's one header row, and lots of "data" rows. However, when I export the report as CVS, the top table gets exported with a new header row, which is the names of the all the columns.
I cannot find a setting which will tell the table or the databand not to export this derived header row. Any suggestions?
Paul J.
CSV Data Export including Column Names as headfer
CSV Data Export including Column Names as headfer
- Attachments
-
- Example Export.xlsx
- Example Export (actually exports as CSV).
- (9.29 KiB) Downloaded 230 times
-
- RPT072-13MonthFluctuationsReport.mrt
- The Report in question
- (37.16 KiB) Downloaded 194 times
Re: CSV Data Export including Column Names as headfer
OK, I found a partial solution. When exported from the designer with "Skip Column Headers" checked, the report rendered without the column header names.
This report was being rendered in code, so I was able to do the following:
I was slightly annoyed to discover that I had to use the version of "ExportCsv" that took a Stream instead of a file name. There is no overloaded version of ExportCsv with the signature (Report, Filename, Settings)
This report was being rendered in code, so I was able to do the following:
Code: Select all
Dim ExportSettings As StiCsvExportSettings = New StiCsvExportSettings()
ExportSettings.SkipColumnHeaders = True
Dim lFileName As String = IO.Path.Combine(_ReportOutputPath, lServerFileName)
Using f As New System.IO.FileStream(lFileName, System.IO.FileMode.CreateNew, System.IO.FileAccess.Write)
lExport.ExportCsv(lSTIReport, f, ExportSettings)
f.Close()
End Using
Re: CSV Data Export including Column Names as headfer
Hello.
We made only most used overloads to satisfy the majority.
Thank you.
Unfortunately, we couldn't provide overloaded method on all possible requirements.Paul J wrote:I was slightly annoyed to discover that I had to use the version of "ExportCsv" that took a Stream instead of a file name. There is no overloaded version of ExportCsv with the signature (Report, Filename, Settings)
We made only most used overloads to satisfy the majority.
Thank you.