calculated field crashes Vs 2005 sp1 ?

Hi!

when I'm trying something litle bit more complex thing than string manipulation in calculated field ex: =RunningValue(Fields!SALES.Value, Sum)

It just crashes visual studio when trying to run the report?! I think this could state as a bug in RS?

RunningValue requires 3 parameters (Expression, function and scope)

Edit Expression dialog may offer a choice with 2 parameters, that is a bug.

|||

Hi!

Thanks for a quick reply, but this did'nt solve this.

Maybe I'll explain little bit
I want to have cumulative sum value over the data. So I open datasource and add new field, and check this field as calculated field with expression : =RunningValue(Fields!SALES.Value, Sum, "DataSource1")

Then I click preview panel and Visual studio waits some seconds and crashes!!!

I really need this beacause Customer needs to have cumulative sales groups

---

Product Sales Cumulative %
A group
Product1 100 100 28%
Product2 70 170 48%
B group 170 48%
Product3 60 230 65%
Product4 50 280 80%
C group 280 80%
Product5 40 320 91%
Product6 30 350 100%

---

And the grouping is dynamic. Ex all cumulative sales less than 0% belongs to the group A sales below 80% belongs to B and others are in group C
At this moment I'm feeling pretty desperate on this case and it seems it is not possible to do this by report services!

|||Aggregate functions are not allowed in calculated fields|||

Seems that I found a solution.
Beacause this cannot be done wiht RS I had load data into data table, do inner calculations and then
pass this data to RS.

I don't understand design decisions of this? Why it's not possible to RS that Headers would accept data from inner fields as a criteria. This report creation process seems to be very waterfall aproach, no precalculations :(

calculated field crashes Vs 2005 sp1 ?

Hi!

when I'm trying something litle bit more complex thing than string manipulation in calculated field ex: =RunningValue(Fields!SALES.Value, Sum)

It just crashes visual studio when trying to run the report?! I think this could state as a bug in RS?

RunningValue requires 3 parameters (Expression, function and scope)

Edit Expression dialog may offer a choice with 2 parameters, that is a bug.

|||

Hi!

Thanks for a quick reply, but this did'nt solve this.

Maybe I'll explain little bit
I want to have cumulative sum value over the data. So I open datasource and add new field, and check this field as calculated field with expression : =RunningValue(Fields!SALES.Value, Sum, "DataSource1")

Then I click preview panel and Visual studio waits some seconds and crashes!!!

I really need this beacause Customer needs to have cumulative sales groups

---

Product Sales Cumulative %
A group
Product1 100 100 28%
Product2 70 170 48%
B group 170 48%
Product3 60 230 65%
Product4 50 280 80%
C group 280 80%
Product5 40 320 91%
Product6 30 350 100%

---

And the grouping is dynamic. Ex all cumulative sales less than 0% belongs to the group A sales below 80% belongs to B and others are in group C
At this moment I'm feeling pretty desperate on this case and it seems it is not possible to do this by report services!

|||Aggregate functions are not allowed in calculated fields|||

Seems that I found a solution.
Beacause this cannot be done wiht RS I had load data into data table, do inner calculations and then
pass this data to RS.

I don't understand design decisions of this? Why it's not possible to RS that Headers would accept data from inner fields as a criteria. This report creation process seems to be very waterfall aproach, no precalculations :(

sql

Calculated field crashes VS

I had a separate post where I was having trouble displaying the entire record in the group header that was that had the max value for the details. http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=641646&SiteID=1

With some help, I used a nested table in the group header, which worked perfectly except when I export the report to Excel (end user requirement) those values are replaced with ''Data Regions within table/matrix cells are ignored.''

For a workaround, I tried adding the following expression to a text box in the detail row of the table.

=iif(Fields!MAX.Value = max(Fields!MAX.Value), Fields!ASA.Value * 100, Fields!ASA.Value)

This will check the max value against the max for the group. If the max value is truely the max, it will multiple the field I am trying to display in the group header by 100. I figured I could then do a max( ) on that field in my group header, but I had no way to reference it. So...I created a calculated field with the same formula - only problem is now VS crashes until I remove the calculate field.

Any ideas why? Or if there is a way to handle this?

It is a known problem that using aggregate functions in calculated field crashes VS. We are considering fixing it in a future release. However, this scenario is not allowed. You'd get an error message when the bug is fixed.|||Thank you! Any other ideas on how I can accomplish the desired results?