Front-End AGGR expression acts differently depending on loading from QVD or not, BUG?

bc5891 — Wed, 23 Jul 2025 14:48:52 GMT

Hi,

I have come across some odd behaviour and wondering if anyone experienced similar. I have created some logic in a table and then using a graph I have a front end expression which calculates the remaining amounts across the time groups.

Once I created/checked the logic I stored it into a qvd and dropped the original table. I loaded from the qvd and the chart is different, even though it uses the same expressions and the number of values in the qvd are the same as the original. The actual values in the qvd are the same but the expression I am using does not work the same way when loading from a qvd.

the expression is as follows:

AGGR(
sum(total <SCH_EVENT_TYPE>{<SCH_YEAR_GROUP = {'Within Yr'}>}SCH_AMOUNT)/1000000
-
RangeSum(Above(sum(SCH_AMOUNT)/1000000, 0, RowNo()-1))
, SCH_EVENT_TYPE, SCH_YEAR_GROUP)

in this I am taking the full value of the initial amount at the first time interval, and then in the next time intervals I only display the remaining values, i.e. the number should always decrease over time. When loading the exact same thing from the qvd though I get the following chart:

Question is: has anyone come across this sort of behaviour before, is it a bug?

I cannot share the application but can assure you that the only difference between the two charts is that one is from a qvd and the other is not, both have the same number of rows and fields.

Thanks

topic Front-End AGGR expression acts differently depending on loading from QVD or not, BUG? in Archived Groups

Front-End AGGR expression acts differently depending on loading from QVD or not, BUG?