After deployment, verify that your data model aligns with the accelerator’s expectations. Ensure your Transactions Datamart includes at least the following fields:
|
Fields |
Data Type |
Description |
|
Unique Id |
String |
Unique identifier of the transaction. |
|
Product Id |
String |
Identifier of the product. |
|
Product Label |
String |
Human-readable product name or label shown in dashboards. |
|
Customer Id |
String |
Identifier of the customer; mandatory if Customer Master is deployed. |
|
Customer Label |
String |
Human-readable customer name or label shown in dashboards. |
|
Revenue |
Money/Number |
Total revenue amount for the transaction. |
|
Date |
Date |
The date used for grouping and filtering transactions (e.g., pricing date, billing date, valid from). |
|
List Price |
Money/Number |
Transaction list price. |
|
Profit |
Money/Number |
Transaction profit. |
|
Quantity |
Number |
Transaction quantity. |
|
Additional waterfall-related fields |
Money/Number |
Optional: Additional fields for waterfall analysis. |
|
Product Hierarchy |
String |
Optional: One or more fields representing hierarchical product groupings used for drill-down and aggregation. |
|
Product Attributes |
String |
Optional: Additional non-hierarchical product attributes available as filters and breakdown dimensions. |
|
Customer Hierarchy |
String |
Optional: One or more fields representing hierarchical customer groupings used for drill-down and aggregation. |
|
Customer Attributes |
String |
Optional: Additional non-hierarchical customer attributes available as filters and breakdown dimensions. |
|
Additional Attributes |
String |
Optional: Any other transactional attributes that you want to use for filtering, grouping, or slicing measures in dashboards. |
Review Period Filter Default
The Review Period filter that appears in the dashboard DATA FILTER panel defaults to the last 12 months of data that has been processed and configured in the configuration model. This means the default date range shown when you first open a dashboard (for example, 2025-03 → 2026-02) reflects the last 12 full months of available transaction data, not a fixed calendar range.
If the default Review Period does not match the date range you expect, verify that:
-
Your Transactions Datamart contains transaction records covering at least the last 12 months.
-
The configuration model has been processed successfully and is in Ready status.
-
The Date field in your Datamart is populated correctly and maps to the field configured as the transaction date in the Insights Configuration Definition.