Hi,

From the looks of the icon, DUREELOCATION is a measure not an attribute. I would be looking closely at the underlying data to see what values exist in this item on each row. Should every row have the same value? My guess is the values are being aggregated in your report, and therefore when you change the rows returned, the aggregate value is different?

Cheers!

MF.

Hi,

From the looks of the icon, DUREELOCATION is a measure not an attribute. I would be looking closely at the underlying data to see what values exist in this item on each row. Should every row have the same value? My guess is the values are being aggregated in your report, and therefore when you change the rows returned, the aggregate value is different?

Cheers!

MF.

Hi David,

without knowing your exact data model and your report I can only suggest some general solutions.

If it's a report, I recommend creating two queries. One for your data incl. filters and another one that only computes the right value for DUREELOCATION. Then join or link those queries together with a real or surrogate key.



Query "Overall AVG Quantity" holds your average, total min/max or whatever calculated measure value and the key column. Query "data" holds all other necessary data columns and the key column for the join.
In my sample I get product lines filtered by country and their quantity from "data" and the overall total without any filtering from "Overall AVG Quantity". The result:
I can filter each country but the overall total for quantity will always be 89,237,091.Another way would be to use induced SQL by writing local SQL directly in one data item of the query but I can only recommend that if you really know what you are doing here.

If the basic filters of your data query should apply to your fixed value, you can write total([DUREELOCATION] for report). You will get the overall sum for all values visible in the report but with background filters applied.

Hi,

From the looks of the icon, DUREELOCATION is a measure not an attribute. I would be looking closely at the underlying data to see what values exist in this item on each row. Should every row have the same value? My guess is the values are being aggregated in your report, and therefore when you change the rows returned, the aggregate value is different?

Cheers!

MF.

Hi David,

without knowing your exact data model and your report I can only suggest some general solutions.

If it's a report, I recommend creating two queries. One for your data incl. filters and another one that only computes the right value for DUREELOCATION. Then join or link those queries together with a real or surrogate key.



Query "Overall AVG Quantity" holds your average, total min/max or whatever calculated measure value and the key column. Query "data" holds all other necessary data columns and the key column for the join.
In my sample I get product lines filtered by country and their quantity from "data" and the overall total without any filtering from "Overall AVG Quantity". The result:
I can filter each country but the overall total for quantity will always be 89,237,091.Another way would be to use induced SQL by writing local SQL directly in one data item of the query but I can only recommend that if you really know what you are doing here.

If the basic filters of your data query should apply to your fixed value, you can write total([DUREELOCATION] for report). You will get the overall sum for all values visible in the report but with background filters applied.

Hi,

From the looks of the icon, DUREELOCATION is a measure not an attribute. I would be looking closely at the underlying data to see what values exist in this item on each row. Should every row have the same value? My guess is the values are being aggregated in your report, and therefore when you change the rows returned, the aggregate value is different?

Cheers!

MF.

Hi,

From the looks of the icon, DUREELOCATION is a measure not an attribute. I would be looking closely at the underlying data to see what values exist in this item on each row. Should every row have the same value? My guess is the values are being aggregated in your report, and therefore when you change the rows returned, the aggregate value is different?

Cheers!

MF.