1 Answer
1

I think this is similar to an issue I had. My issue was that the nodeset definition wasn't correctly identifying rows. I am guessing this has to do with the grouping being by date. Could you include the definition of the $nodeset from the template? You may have some luck of converting the date into a string to group by?

You are right my questions is very similar to your issue. I had reviewed your post first before posting my question. There are many reasons, but one main reason why I know that it is not the date format or column that is causing the issue is because I am calculating a total sum for one the numeric columns as well. The sum has the same issue. The total is correct for the last group but zero for all others (I also tried deleting the last group to see what happens. In this case the initial second to last group became the last group and had correct calculation and all other group were zero).
–
ssvvMar 13 '12 at 17:13

I noticed in your post you defined 'nodeset'. I have pasted my code with code parameters, I would appreciate if you can tell me how I can define the 'nodeset' to include all rows in a group. Or if there is a way I can use dsQueryResponse to generate the group count. Thanks.
–
ssvvMar 13 '12 at 17:14

You posted your code from your template definition. The 'nodeset' is defined further up when the template is called look for <xsl:call-template name="dvt_1.groupfooter0"> up in the body template definition. In that section, it defines the nodeset to be used in that footer and it sounds like that needs adjusted.
–
cfooteMar 14 '12 at 14:58

Did you get your solution working? I am interested to hear how you solved it.
–
cfooteMar 23 '12 at 19:31

1

Thanks for the feedback. I found the solution. It turns out I cannot group based on mm/dd/yyyy date format. In order for me to group and get correct column totals the date must be in yyyyMMdd format. So I added a calcuated date column with yyyyMMdd format and it worked. Thank you vey much for your help.
–
ssvvMar 29 '12 at 16:20