CSV rendering is missing first detail row

For one report we've designed, an HTML rendering will produce 3 detail
records. When this same report with the same parameters is rendered in CSV,
the first detail row is missing from the output. All other aspects of the
export seem to work as expected.
This occurs with several reports we have but not all of them. This happens
when previewing in VS.NET, RS Manager, and on our live Web site. Other
formats do not drop the first detail record.
Is there any resolution to this problem?FYI: I experienced the same problem you described. Through trial and error I
determined that what was causing the problem was that I was grouping the
Details section of the Table. To work around this I added grouping to the SQL
code and removed grouping from the report detail.
Brad
"John Demar" wrote:
> For one report we've designed, an HTML rendering will produce 3 detail
> records. When this same report with the same parameters is rendered in CSV,
> the first detail row is missing from the output. All other aspects of the
> export seem to work as expected.
> This occurs with several reports we have but not all of them. This happens
> when previewing in VS.NET, RS Manager, and on our live Web site. Other
> formats do not drop the first detail record.
> Is there any resolution to this problem?

CSV rendering is missing first detail row

For one report we've designed, an HTML rendering will produce 3 detail
records. When this same report with the same parameters is rendered in CSV,
the first detail row is missing from the output. All other aspects of the
export seem to work as expected.
This occurs with several reports we have but not all of them. This happens
when previewing in VS.NET, RS Manager, and on our live Web site. Other
formats do not drop the first detail record.
Any ideas? I can't seem to find anyone else that has run across this
problem in the groups.I continue to have this problem and cannot find any answers. Is there a
problem with the CSV rendering extension?
"John Demar" wrote:
> For one report we've designed, an HTML rendering will produce 3 detail
> records. When this same report with the same parameters is rendered in CSV,
> the first detail row is missing from the output. All other aspects of the
> export seem to work as expected.
> This occurs with several reports we have but not all of them. This happens
> when previewing in VS.NET, RS Manager, and on our live Web site. Other
> formats do not drop the first detail record.
> Any ideas? I can't seem to find anyone else that has run across this
> problem in the groups.
>|||John,
I am also seeing the same results with the missing first line. Does anyone
know if this is a known issue or just a setting that can be set?
"John Demar" wrote:
> I continue to have this problem and cannot find any answers. Is there a
> problem with the CSV rendering extension?
> "John Demar" wrote:
> > For one report we've designed, an HTML rendering will produce 3 detail
> > records. When this same report with the same parameters is rendered in CSV,
> > the first detail row is missing from the output. All other aspects of the
> > export seem to work as expected.
> >
> > This occurs with several reports we have but not all of them. This happens
> > when previewing in VS.NET, RS Manager, and on our live Web site. Other
> > formats do not drop the first detail record.
> >
> > Any ideas? I can't seem to find anyone else that has run across this
> > problem in the groups.
> >

CSV exporting issue

Hi,

I have a simple report with a table and 3 columns. I have used only the detail row of the table to display data from a simple dataset that has a stored procedure as the data source.

When I export it to CSV format, the names of the textboxes that are in the table column also gets exported in the first row. Is there a way to suppress this?

I have already tried setting DataElementOutput = NoOutput for the table and the textboxes but nothing works. Please do not give me the link of an earlier thread on the same topic because that doesnt provide the answer.

I have also tried setting DeviceInfo parameters in RSReportDesigner.config and rsreportserver.config (NoHeader=true) but none of them work even after restarting the machine and SQL Reporting Service.

If there is a way or an alternative, please let me know.

Thanks,

Shyam

There is another issue with CSV exporting.

I want every field to be wrapped around double quotes, so I have handled that in the SQL query itself. When I export to CSV, it adds 4 more double quotes to every field which means every field has 6 double quotes around it (3 to the left and 3 to the right). I also tried handling it in the report by appending Chr(34) and an explicit double quote in the field expression but all of them seem to give the same stupid result (6 double quotes).

Is there a way to work around this problem in SQL Reporting services?

It's very frustrating.

Shyam

|||

Thanks everybody for not responding. Hope it works on another machine.

Shyam

CSV exporting issue

Hi,

I have a simple report with a table and 3 columns. I have used only the detail row of the table to display data from a simple dataset that has a stored procedure as the data source.

When I export it to CSV format, the names of the textboxes that are in the table column also gets exported in the first row. Is there a way to suppress this?

I have already tried setting DataElementOutput = NoOutput for the table and the textboxes but nothing works. Please do not give me the link of an earlier thread on the same topic because that doesnt provide the answer.

I have also tried setting DeviceInfo parameters in RSReportDesigner.config and rsreportserver.config (NoHeader=true) but none of them work even after restarting the machine and SQL Reporting Service.

If there is a way or an alternative, please let me know.

Thanks,

Shyam

There is another issue with CSV exporting.

I want every field to be wrapped around double quotes, so I have handled that in the SQL query itself. When I export to CSV, it adds 4 more double quotes to every field which means every field has 6 double quotes around it (3 to the left and 3 to the right). I also tried handling it in the report by appending Chr(34) and an explicit double quote in the field expression but all of them seem to give the same stupid result (6 double quotes).

Is there a way to work around this problem in SQL Reporting services?

It's very frustrating.

Shyam

|||

Thanks everybody for not responding. Hope it works on another machine.

Shyam