excel calculation works only for the first cell for each group

[nskatzis]

Hello,

I have an excel report with grouping.

Everything works perfect, instead of the calculation between two fields in the report.

As you can see in the two screenshots, it calculates only the first row from each group.

I don't know the reason, but I followed the guideline here:

https://help.qlik.com/en-US/nprinting/February2021/Content/NPrinting/ExcelReports/Make-Calculated-Co...

Qlik nprinting version: 22.15.11.0

Qlik sense: May 22, Patch 1

Thank you in advance,

Nikos

[Lech_Miszkiewicz]

You did not build your template properly so this si working as designed. You need to build your template using excel based tables or levels for formulas to work. This is obviously all documented on official help page  tutorial here: 

https://help.qlik.com/en-US/nprinting/May2022/Content/NPrinting/ExcelReports/Make-Calculated-Column....

cheers

[nskatzis]

Could you give me an example of what is build not properly in the report I sent?

I repeat, the levels work perfect and I get the results I want

[Lech_Miszkiewicz]

Are the highlighted fields coming from level - I assume they are not! am I right?

[Lech_Miszkiewicz]

lso to add to the above - if the cells highlighted by me are coming from the table they don form excel table (they are just forming range of cells).

Again - read documentation please and pay attention to details as this is all explained there. I have given you the link you need so it is just a matter of studying it and applying required changes.

cheers

[nskatzis]

I created Group_3 with only one field for levels.

That was the only way I could found to succeed the desired grouping.

And of course, the highlighted information comes from the table (Group_3 has only one field).

If I use the levels from PM Sum table (instead of Group_3), the grouping was not correct.

In any case, I can add this calculated field to Qlik Sense.

Thank you

[Lech_Miszkiewicz]

You can nest levels within the levels. 
Group3 level can stay as is, but content you put as a table could be brought in as another level nested inside-then calculated field would work. 
and yes-you can always add it in Qlik Sense-in this scenario it would be the best option anyway for performance purposes