Hi
Please see the image and cs code file.
formula for column RATE: if( [TOTAL] <>0 , [FAIL] / [TOTAL], dbnull() )formula for summary of column RATE : if( [TOTAL()] <>0 , [FAIL()] / [TOTAL()], dbnull() )summary type for column NG_KG is sum.
The first image works properly with the original value in the grid, but when the value on the cell (column NG_KG) in modified from 45 to 60, the summary value on the column RATE also changes strangely.
Is it a bug?
Thanks
Hi,
The cs code attachment, it seems that there is only one attachment for one post, :-(
By the way, this problem only happens when there are grouped columns on the groupby box, really strangely.
Hope this problem will be fixed in the near future.
Can you post a small sample project demonstrating this issue? We are not aware of any problems like this with the latest version of the controls. Your sample cs file doesn't really help, because there's too much missing, like what version you are using.
You seem to have simply re-iterated your description of the problem here without answering my question. I understand all of that, already.
The question I am asking is...
Is there some connection in your application between the NG_KG summary and the Rate summary that I am not seeing?
It seems to me that the NG_KG summary should have NO effect on the Rate summary at all. Is that correct. I just want to confirm that that is the behavior you are expecting.
As you can see,the formulas in the attached project source code, there is nothing connection between the column/summary NG_KG and RATE and I do NOT want such connection (also NOT my expecting), just the UltraGrid calculates the wrong smuarry value as I described in the last post.
Okay, that's what I wanted to confirm.
This appears to be a bug in the controls. So I'm going to forward this thread over to Infragistics Developer Support and ask them to create a case for you and write this up as a bug for developer review.
OK, hope it will be fixed in the near future.
Hello Felix,
CAS-98958-L6M9Y4 has been created for this issue. I have logged this issue with our developers and will provide additional details via the case. I will post again here when the issue has been resolved.