Do you understand SQL? Just think of your chart like an SQL statement. Your dimensions are your GROUP BY clause. The total line is like an extra select unioned to the first. Since you have sum of rows specified for the first two expressions, it's implicitly doing the sum(). So our chart with its summary line and the simpler expression is something like this:
SELECT
InvoiceNO
,PurchaseAmount
,SoldAmount
,1-PurchaseAmount/SoldAmount as Profit
FROM INL14A
GROUP BY InvoiceNO
UNION ALL
SELECT
'Total' as InvoiceNO
,sum(PurchaseAmount) as PurchaseAmount
,sum(SoldAmount) as SoldAmount
,1-PurchaseAmount/SoldAmount
FROM INL14A
That's not legal SQL. In the first select, you have a group by, so you MUST use an aggregation expression on fields that are not in the group by. The second select is inconsistent, sometimes using a sum(), and sometimes not. I suspect that isn't legal either.
Now, QlikView doesn't strictly require an aggregation expression with a group by the way SQL does. Or perhaps more accurately, there's an implied aggregation expression of only(). For clarity, I recommend EXPLICITLY stating the aggregation expression in all cases, even if it IS only(). I recommend pretending that QlikView is enforcing the SQL rule.
Now we get to my solution. All my solution said was to be consistent in the second "select". You were summing for the first two columns, so you needed to sum for the third. Since you couldn't use "sum of rows" to do this, you had to do it explicitly with sum() functions.
But since I've already written all of this (I was trying to be brief before), I might as well tell you that the solution I gave you is NOT the solution I would personally use. I would use "expression total" for all the total modes. I would use the sum() explicitly in the PurchaseAmount and SoldAmount columns rather than using "sum of rows". I would name the columns Purchase Amount and Sold Amount. And then I'd calculate % Profit using the column names to avoid doing the sum()s a second time. (Or at least I suspect that internally, QlikView would do them a second time. It's possible it's clever enough to recognize that it's already done the calculations, but I'd rather just explicitly tell it it's already done the calculations by referring to the column names.)
Dimension = InvoiceNO
Purchase Amount = sum(PurchaseAmount)
Sold Amount = sum(SoldAmount)
% Profit = 1 - [Purchase Amount]/[Sold Amount]
