-
1. Re: Question 1 of 3 concerning Summary Reports - Exporting
did you use the "group by" option? Did you specify the summary fields as part of the fields from which you are exporting data?
-
2. Re: Question 1 of 3 concerning Summary Reports - Exporting
On the export, I tried it both ways, with and without the group-by. The summary field is included in the export. All the levels use the same zcCount field from the file to do the totals. I am suspicious that that may be the hassle here.
-
3. Re: Question 1 of 3 concerning Summary Reports - Exporting
Please explain what you mean by:
All the levels use the same zcCount field from the file to do the totals.
exactly HOW do you use that field?
-
4. Re: Question 1 of 3 concerning Summary Reports - Exporting
As you can see in the previous screen shot there are three fields used for counting up tickets and their status
zsTicket = Summary, Count of Job_Ticket_ID
zsClosed = Summary, Count of ztClosed (aka Calculation Indexed, = Close_Date >0)
zsOpen = Summary, Count of ztOpen (aka Calculation Indexed, = Case(Close_Date = "Open";1;GetAsNumber(""))
So, each level of summary in the report will sum up for that line. (I give Dave Doweling the credit for showing me this idea)
-
5. Re: Question 1 of 3 concerning Summary Reports - Exporting
Yes, that was pretty obvious. But your statement refers to a field named zcCount--which is not mentioned at all in your last post and thus I am making sure that there is no missing key detail here before I make any further suggestions.
Assuming that zcCount is NOT a factor here, you should be able to use the "group by" option, specify the summary fields and get an export where each row of exported data matches to a row of data in the summary report--but only if you have sorted your records the same way in each case.