Problem / Question with DataSet in SSRS 2005

  • I have a dataset which is calling a stored proc in my SSRS 2005 report. The stored proc just returns one value which is the result of a SUM in my stored proc's sql query.

    When I reference that field from my dataset, SSRS puts SUM() around the fieldname. This is causing an issue because I have a complicated expression in my table footer and need to just reference that field by it's name without SUM.

    Why is it putting SUM around my one field? If I take out the SUM around that field, SSRS can't recognize it as a valid dataset field anymore

    also, check out my other thread related to this: http://www.eggheadcafe.com/forums/ForumPost.asp?ID=60046&INTID=9

  • This was removed by the editor as SPAM

  • having the sum in your expression will not make much of a difference to what you want to achieve.

    what problems is it causing?


    Everything you can imagine is real.

  • I ended up having to do a retarded workaround. I had to call my stored proc to move the result into a table then call another stored proc to retrieve that value from the table...then I was able to reference it without a SUM() around the field that the stored proc returned.

  • what problems is the sum causing, because the method you have chosen is not a very bright idea as you have said.


    Everything you can imagine is real.

  • what do you mean the method chosen isn't a bright idea.  So you're saying using a stored proc initially to bring in one value is bad?  The stored proc is running a bunch of sql queries and bringing back a calculation of days (based on subtracting vacation days from a sql table, etc.).  The problem is that SSRS treats that one value as a SUM.  It's not the way I'm doing it, using a stored proc, it's the way SSRS treats the one value coming from the stored proc.  The workaround was the only way I could get SSRS not to recognize my value as a SUM coming from my dataset's stored proc.  I have no clue what your last post means.

  • sorry if i caused you any offense, but i was thinking that your other line i.e.

    meant it was not as good idea.

    sorry once more for the misunderstanding.

    now for your post response. I am saying when you run the report you should not have a problem even if you use the field name with a sum() in an expression. That is why i am asking what problem you are having when you run the report.


    Everything you can imagine is real.

Viewing 7 posts - 1 through 6 (of 6 total)

You must be logged in to reply to this topic. Login to reply