Predict - Troubleshooting

Possible Causes & Solutions

1. Non-Numeric Fields May Be Involved

If your Balance Sheet model includes non-numeric fields (e.g., comments, text), aggregation will not apply to those fields.

Solution: Ensure that the measures you are trying to aggregate are numeric and not tagged as non-numeric. Non-numeric fields must be used for reference or qualitative data and are excluded from rollups or calculations by design.

2. Hierarchy Configuration Issues

Aggregation relies on correct hierarchy setup (roll-up levels and parent-child relationships).

Solution:

Check the following in Hierarchy Management:

• All accounts have a defined parent.

• Rollup operators (e.g., +, ~) are properly configured for each node.

• No duplicate codes or naming conflicts exist.

Also, ensure that you are not using Alternate Hierarchies that may behave differently in certain aggregation scenarios.

3. Formula Conflicts in C-Type Lines

If a line in the Balance Sheet model is defined as a CALC (C) type row, it will override aggregation and use the specified formula.

Solution:

Review the template setup:

• Go to Template Setup > Line Details.

• Check if the affected line is a C-Type with formula.

If aggregation is needed, either remove the formula or ensure the formula includes all necessary child lines.

4. Scenario Lock or Closed Periods

If the scenario is locked or contains closed periods, aggregation will not reflect changes even if the data is correct.

Solution:

• Unlock the scenario temporarily.

• Open closed periods if aggregation is expected in those columns.

5. Expedited Loading Mode

If the template uses Expedited Loading, aggregation or data visibility (such as hidden rows or columns) may behave differently.

Solution:

Check Template Settings:

• Navigate to Planning Control Panel > Template Setup.

• If Expedited Loading is enabled, try disabling it and reloading the template to verify aggregation behavior.

6. Incorrect Account Mapping or Reference Setup

If Destination, Reference, or History mappings are incorrectly configured or incomplete, it may affect how data aggregates at higher levels.

Solution:

• Use the new Template Mapping UI to verify all mappings (Destination, History, and Reference accounts).

• Make use of the Show Errors Only toggle to highlight mapping issues.

Note: If still it’s not working, contact Planful Support to review backend hierarchy settings.