Learn more in the Cube summary table configuration topic.
General page
After filling out the fields on the General page, save the definition. Saving the definition creates the Data Table and associates it with the summary table. The Data Table is the table you’ll query in a logic block when fetching data from the cube summary table.
Optionally, select the Enable Record Log checkbox to track the summary table records' processing status. When selected, the Record Log Table which stores the record log data is automatically created at the time of save. Learn more in Track processed summary table records.
Data page
Select your data sources for the cube summary table, and create unique names for different types of events, such as a transaction for posting an invoice and a transaction for voiding an invoice. This allows you to apply different metrics, dimensions, and logic blocks to different types of transactions.
Optionally, create filters to limit the records which are tracked by the summary table. Records that match the filter criteria initiate the event. If a record matches multiple filters, it runs both events. If a record matched filter criteria, but then changes to not match the filter, it is removed from the summary table.
Dimensions page
Define the dimensions which form the summary table. Dimensions are used to categorize how records are summarized. Every record tracked by this summary table will be converted into a dimension set, and applied to the summary record matching all of its dimension values.
All dimensions added on this page must also have data mappings assigned from one of the data sources specified.
Metrics and Display Fields page
Select the metrics you want included in the summary table. Metrics are numeric summaries of dimension values, and are continuously updated by new transactions that impact the summary table.
Optionally, use the Display Fields subtable to configure display fields you want included on the summary table. Display fields are non-categorical values that are attached to summary table records that don’t fit into the dimension or metric categories. For example, Unit of Measure or Computation Method.
Transactional Event Logic Blocks page
Create the logic block you want used for any logic block calculated metrics, as well as any display fields.
Save the definition to create the Transactional Event Logic Block Table. Any changes saved to the definition are also reflected in the table. This means the transaction event table always contains the fields defined in the summary table.
You can also run a logic block each time a transaction is processed in the table. Select the name of the logic block in the Transactional Event Logic Blocks subtable.
Optionally, make fields from transaction data sources available to transactional event logic blocks in the Transactional Event Work Fields subtable.
Cube summary table configuration
Configure a cube summary table with the Cube Summary Table Definitions application and the Logic Block Builder.
Configure your cube summary table with the following applications:
- Cube Summary Table Definitions application—Build your summary table definition. Use application links and form actions to navigate to the Logic Block Builder and Summary Table Activations application as needed.
- Logic Block Builder—Configure a transactional event logic block which calculates and assigns logic block calculated metric and display fields.
- Summary Table Activations application—Activate your summary table so it starts to run and receive data. Mark as Primary when you want your summary table to begin being queried by the system.
Cube Summary Table Definitions
In the Periodic Summary Table Definitions application, you must:
- On the General page, optionally select the Enable Record Log checkbox to track the summary table records' processing status. When selected, the Record Log Table which stores the record log data is automatically created at the time of save. Learn more in Track processed summary table records.
- On the Data page, in the Data Sources subtable, select your data sources for the summary table.
- Optionally, use the filter to refine which transactions from the data sources are added to the summary table.
- On the Dimensions page, define the dimensions you want included in the summary table.
- In the Dimensions subtable, add your dimension. The order in which you enter the dimensions controls the index ordering, so enter them in the order of importance.
- In the Dimension Data Mappings subtable, add an entry for each dimension.
- Save your summary definition. This automatically creates the transaction event logic block table.
- On the Metrics and Display Fields page, define your metrics and, optionally, any display fields you want included in the summary table.
- In the Metrics subtable, add your metrics and select they should be calculated. Calculations can be system aggregated or logic block calculated for more complex calculations and conditionals.
- In the System Aggregated Metric Data Mappings subtable, add an entry for each metric that is system calculated, and map the field from the data source that is needed for the calculation. For example, a metric for transaction amount must have the transaction amount field mapped from the data source in order for the system to calculate the transaction amount summary value.
- Optionally, use the Display Fields subtable to configure display fields that you want included on the summary table.
- On the Transactional Event Logic Blocks page, save your definition to create the Transactional Event Logic Block Table. Then, select the Create Transactional Logic Block button to open the Logic Block Builder to configure your transactional event logic block.
Logic Block Builder
In the Logic Block Builder, create your transactional event logic block of type Cube over the Transactional Event Logic Block Table. The logic block is run during a transaction event to calculate and assign logic block calculated metrics and display fields.
Optionally, include additional complex calculations which should be applied to records as they are processed in the summary table.
Cube Summary Table Definitions
On the Transactional Event Logic Blocks page, in the Transactional Event Logic Blocks subtable, select the logic block that you want used for any logic block calculated metrics, as well as any display fields.
- Optionally, in the Transactional Event Work Fields subtable, map fields from your transaction tables that you want available in your logic block.
Once you have configured your cube summary table, select the Activate form action. Activating a summary table makes it receive data from the transactional tables it references.
Summary Table Activations
In the Summary Table Activations application, view current versions, also called activations, of summary tables. There can be multiple activations built over the same summary table. Select the Make Primary Activation row action on your summary table to make it the Primary table which the system references when the summary table is queried by outside reports.