Friday, February 01, 2013 3:24 PM
We are using SSRS 2005 reports web service to export report data to CSV format.
This report specific stored proc returns result set with columns having decimal type value e.g. 12345.32,.
But generated CSV report not showing the values for these columns.(blank value shown instead)
It can show value on report only if we pass hard coded value from SP, but the recorde selected from temporary table not appearing on the report.
Friday, February 01, 2013 3:41 PM
You can control the export behavior on a textbox with the DataElementOutput property. By default, this is set to "Auto", you can set it to "Output".
Select the textbox > go to properties > set the DataElementOutput property to "Output".
Hope it helps.
Friday, February 01, 2013 4:08 PM
Tried this not working...
This is very strange if I hard code the values in SP it appears on report but not the values selected from the table.
Friday, February 01, 2013 4:12 PM
I'm from the same team : We tried format, formatnumber,Cdec, Cstr etc.
Also we tried a IsNothing() function to see what SSRS sees, we found out that everything is being ealuated as True, means ISnothing = True even though our stored procs are dispalying the values + the Preview mode of the SSRS in VS2005 shows the values.
Only after we deploy the rdl to the report server - the values dissapear irrespective of whatever formatting/casting we do.
We even converted the values to string, varchar, nvarchar in teh sproc before sending to the rdl but still no use
- Edited by Chetan Handa Friday, February 01, 2013 4:14 PM typo
Monday, February 04, 2013 11:52 AMModerator
Does the report run properly on the report server? If so, does the issue happen with the CSV file exported from the report manager? If you pass multiple-value parameter to the stored procedure, please note that the array values are not supported by stored procedure. To work around this, we need to pass string value to the store procedure, and then use a custom function to split the string value. For more information, please see:
Using MultiValue Parameters with Stored Procedures in SSRS
Besides, Reporting Services supports stored procedures that return only one set of data. If a stored procedure returns multiple result sets, only the first one is used.
@Chetan, hope this information helps you too.
TechNet Community Support
Monday, February 04, 2013 1:59 PM
Hi Mike, we are using simple parameters and passing it in a regular way.
Issue is with the data which is coming from the sproc is not visible on the final report output (csv)
(a)when we execute the sproc its visible
(b)when we bind that sproc to the rdl and see it in preview mode its still visible
(c)When its uploaded to the report server and executed via the execution asmx the results dont show anything
The original datatype is float in the table, we are casting it to decimal before summation and displaying it
We experimented with a lot of combinations and found these strange observations:
 If I display as alphanumeric string e.g append xyz to the column value after casting it it will appear as 123.1234 xyz in the sproc
then if I see it in preview mode it will still appear as 123.1234 xyz
but after running it via the SSRS server it appears as just 0.00 xyz ..the numeric portion is wiped out
 If we retreive value from a different column of same datatype but from a diff table and bind it to the rdl it works
But when i bind it to the original table's column it doesnt work.
 If I hardcode the value into the column via the select query e.g "select 123.12" instead of "select column1" it works great.
Its visible in the sproc output, rdl preview as well as the server side.
 IF I add 0.001 to the value it apears correctly in the sproc output, rdl preview mode also..
e.g select (Column1+ 0.001) the results are correct
but on the server it becomes 0, so the results are 0.001 for all the columns as if the column had value of 0
Combinations of casting the column value to diff formats, including varchar etc and corresponding formats in rdl have been tried out ..
- Edited by Chetan Handa Monday, February 04, 2013 2:01 PM typo