The aggregate functions (For example, MIN, MAX, AVERAGE, etc.) do not apply to the measure, while generating query. Why?

• Related Articles

• Aggregate functions such as MIN, MAX, AVERAGE etc donot apply to the measure at the time of query generation

  The aggregate functions donot apply for the measures that are created by referring the Dimensional tables (E.g. DIM_STORE). The aggregate functions apply only when the measures refer Aggregate tables (E.g. AGG_MLY_STORE). This is the functionality of ...

• Why the Aggregate functions such as MIN, MAX, AVERAGE etc is not applying to the measure at the time of query generation?

  The aggregate functions do not apply for the measures that are created by referring the Dimensional tables (E.g. DIM_STORE). The aggregate functions apply only when the measures refer Aggregate tables (E.g. AGG_MLY_STORE). This is the functionality ...

• When I add a base measure with average aggregation, the Total field should show the average value. But why is it showing the sum of that average?

  The sum of the average is displayed in the 'Total' field becauase the functionality is to display the total value and not the average value. When you add a base measure with average aggregation, it considers only the line items and not the 'Total' ...

• While adding a base measure with average aggregation then, the total field should show the average value, but it shows the sum of that average. Why?

  Whenever the aggregate functions are applied, it will consider only the line items but not the TOTAL column. Total field always displays the summed-up values from the line items.

• I have created Product Attributes, ex: SKU Size, SKUAge etc. , same is not created as measure automatically in Base measure list. Why?

  This problem occurs because the attribute is mapped to the same DB column as that of the pre-existing base measure. We can manually create base measures with two different names but map it to the same DB column. However, if we are expecting a ...