Database reference guide |
HOME |
AggregatesAggregate Columns provide a mechanism for analyzing data in summary from across one or more tables. This section gives an overview of aggregate creation in Engine but it is worth noting that the Campaign Manager Help section covers specifics of creating aggregates in the application. With aggregate functions, it is possible to determine values such as the number of people in a family, the total transaction value for a customer, the number of purchases made for a particular geographic region or the first Order Date for a specific customer. In order to create an aggregate, a relationship is required between 2 tables - either as a direct link between the tables, or as an indirect link via intermediary tables. The simplest form of aggregation is a COUNT, which can be created by specifying two table names, i.e. Count of Customers in each Household. All other aggregations require a numeric field as input for the function column, where the function column is the column summarized in the aggregation i.e. Last Purchase date using Purchase Date on the Order table, summarized to a Customer table to provide a single date for each Customer. Rules for creating AggregatesAs for any field within Engine, an aggregate field must be created on a table. This table is referred to as the Resolution or Owner Table of the aggregate and must be on the ONE side of a The function column - the column that is going to be summarized - always comes from the MANY side of a In the data structure below, it is possible to create aggregates on the CUSTOMER or ORDER tables, but not on the ORDER DETAIL table. The following aggregate fields could be created given the data structure provided;
Types of AggregateThe following table lists the type of aggregate fields that can be created.
Operational Elements of an Aggregate
|
Online & Instructor-Led Courses | Training Videos | Webinar Recordings | ![]() |
|
![]() |
© Alterian. All Rights Reserved. | Privacy Policy | Legal Notice | ![]() ![]() ![]() |