Hopefully I can change this to a question and break the trend
Your comments needed, thanks.
[Detailed Sales Product by Customer:6,5, 6, 3, 3, 1, 2]
>CUSTOMER|ITEM GROUP|ITEM|PORTION|QTY|TOTAL
{REPORT ORDER DETAILS:EC.Customer.Full Name.asc,O.ItemGroup,O.MenuItemName,O.PortionName,O.Quantity,O.ExactTotal:(ODI=True) && (TCET=Customers)}
>> TOTAL|||||$[=F(TN('{REPORT ORDER DETAILS:O.ExactTotal.sum:(ODI=True) && (TCET=Customers)}'),'#,#0.00')]
EDITED:
Ok Emre I know what it is doing, by the use of “.asc” it is eliminating duplicates and therefore SAME ORDER LINES are being removed. The use of “.asc” I thought would be to SORT ONLY and not sort + remove duplicates as customers will reorder the same Drink.
That above syntax is a bit misleading I am really referring to the “.desc” or “.asc” - forget about SUM as this works ok for our reports. The Sorting by itself removes duplicates which is undesired as 2 drink orders by same customer for same drink need to be shown.
I wonder if there is a bug in there somewhere when it comes to ASC/DESC?
For example, maybe it is treating ASC (or any trailing .something) as though it is an aggregate when in fact this is not always the case. SUM and COUNT are aggregates, but ASC, DESC are not. Maybe that is the bug?
P.S. sorry, I just blurted out my first answer without actually looking at your Report to see what it was doing, because it was the first thing that popped in to my head when it comes to reporting with SUM that most people don’t understand. Still a good point to keep in mind.
Ok a possibility but I think the Customer desired to se each order but then again summing O.Quantity why waist the paper Nice could be a workaround for the time being while Emre emerges from wherever he is
EDIT:
Tested and works well! Not sure if I should mark it as a solution in case there is an issue and it just gets pasted over? Thanks as always Q!