Configuration Information (Insights Dashboards)

The Configuration Information table holds definitions configured during model configuration. The main purpose of the Configuration Information table is to act as a diagnostic log of how the model interpreted and cleaned up the configuration, and to surface any warnings from the calculation in the Review step, without affecting the aggregated Datamart Tables themselves. The table is used to:

• Explain Automatic Clean-up of Inputs – When duplicate fields are detected across inputs, and one of them is automatically removed based on a priority order. The messages specify which field was removed, where it came from, and which field was kept.

• Warn About Configuration/Data Quality Issues – Such as fields that are expected to be extended (per quantity) but are not. This covers the Reference Price input (with additional automatic conversion in Aggregated Transactions) and Waterfall fields (warning only, no automatic conversion).

• Provide General Calculation Warnings – Warnings are provided at once place, so that administrators can quickly see how the configuration was applied.

Properties

• Name – ConfigurationInformation

• Label – Configuration Information

• Table Type – JSON

• Value Type – JSON

Definition

• Required – Yes

• Impact on Aggregated Datamart Tables – No

Warnings

The Configuration Information table currently displays messages in the following cases:

Duplicate Fields

When the same field is selected more than once across inputs (for example, both in Product Attributes and Product Hierarchy, or both in Transactions and another source), the model keeps only one occurrence based on a predefined priority and removes the duplicate field from scope.

Warning Message Example

The following field: "Customer Type" in Customer source’s Customer Attributes input was removed from scope as it was duplicated with "Customer Type" in Transactions source’s Customer Hierarchy input.

Unextended Fields

For some inputs, the model expects fields to be extended (per quantity). If such a field is not extended, a warning is added to the Configuration Information table.

Reference Price

If the selected field is not extended, the model still performs the calculation and automatically multiplies the field by Quantity in the Aggregated Transactions table.

Warning Message Example

The field: "Reference Price" is expected to be extended (per quantity) but it does not seem to be.

Waterfall Fields

If a Waterfall field is not extended, the model does not convert it automatically.

Warning Message Example

The field: "Surcharges" is expected to be extended (per quantity) but it does not seem to be.

Missing Data Range

After applying the Transactions tab filters to the datamart, the actual transaction data may not fully cover the time windows expected by the model.

Missing Data in Selected Date Range

The filtered Datamart data starts later (or ends earlier) than the Date Range selected in the model.

Warning Message Example

Missing data in time range. The date filter applied on Transactions data from Transactions tab results in data from 18/06/2025 to 31/12/2025. However, the Date Range selected from this input covers the data from 01/01/2023 to 31/12/2025.

Missing Data for Previous Period

The filtered Datamart data does not fully cover the previous period that is required for Prior Revenue and Prior Profit calculations.

Warning Message Example

Missing data for previous period. The date filter applied on Transactions data from Transactions tab results in data from 18/06/2025 to 31/12/2025. However, the previous period (used for Prior Revenue and Prior Profit calculations) is from 01/01/2024 to 31/12/2024.

Example Values

See Also

• Review Step (Insights Dashboards)