This parameter should be used on the aggregated view, which will allow Omni to match the aggregated table to the underlying views it aggregates.Documentation Index
Fetch the complete documentation index at: https://docs.omni.co/llms.txt
Use this file to discover all available pages before exploring further.
Syntax
Properties
An array of field names from the base table that correspond to columns in the aggregated view, specified as
view_name.field_name.The name of the base view that this aggregated view summarizes.
Examples
In this example, you have anorder_items table that contains a few metrics. Using aggregate awareness, you can create a user_facts table that rolls up these metrics. Let’s take a look at how the fields in the underlying views will map to the fields in the aggregated user_facts view:
| Underlying view fields | Aggregated user_facts fields | |
|---|---|---|
users.id | becomes | user_id |
order_items.created_at[month] | becomes | month |
order_items.count | becomes | count |
order_items.total_sale_price | becomes | total_sale_price |
user_facts.view file would look like this:
user_facts.view file
user_facts view:
SQL for user_facts table