Maintenance - Troubleshooting

User cannot be saved. No. of Administrators exceeds the maximum limit set.

Your organization has reached the maximum allowed number of Administrator users based on the limits configured. This restricts adding new users with the Administrator role.

Contact Planful Support to extend the maximum number of allowed Administrator users.

Once the Planful Support team confirms the limit has been increased:

1. Navigate to Maintenance > Administration > User & Role Management.

2. Add the new user and assign the Support Role as Administrator.

3. Click Save.

You will now be able to successfully create an Administrator user.

Scenario not showing in DLR

• User doesn’t have scenario access

• Scenario not forwarded

• Scenario is not active

1. Contact admin to assign access via Scenario Setup or User & Role Management.

2. Ensure scenario is forwarded.

Cannot enable Data Seeding in a scenario / Data Seeding option is disabled in my copied scenario

• The Enable Data Seeding checkbox can only be selected during scenario creation.

• Once the scenario is created and saved, whether you are editing an existing scenario or working with a copied scenario where Data Seeding was not enabled, this option becomes read-only and cannot be changed.

To use data seeding, you must create a new scenario and ensure that Enable Data Seeding is selected during the setup process.

I changed my debit/credit in Account Hierarchy Management. Why did it only reflect in my Actual scenario and not in my Forecast?

• The Actual scenario always reflects hierarchy updates immediately.

• Forecast and Budget scenarios store closed period data, which does not auto-refresh when changes are made in Account Hierarchy Management.

• As a result, debit/credit changes appear in Actuals but not in Forecast.

1. Go to Maintenance > Administration > Scenario Setup.

2. Select the impacted Forecast scenario and click the More icon.

3. Run Refresh Closed Period Data.

4. Reopen your Forecast reports/templates to confirm the debit/credit change is applied.
   Note: Running this process updates closed period data in Forecast so it aligns with your hierarchy updates.

Planful (Beta) (Custom) connector not visible in Power BI

• Missing .pqx file

• File not saved in correct folder

1. Download .pqx file from from the Configuring Planful Connector for Power BI article.

2. Save to Documents > Power BI Desktop > Custom Connectors.

Values appear multiplied when uploading .txt files via a DLR.

Currency Conversion is set to Yes in the DLR, multiplying values based on defined Exchange Rates.

1. In Define Overall Rule Settings, set Currency Conversion to No if not needed.

2. Verify the Exchange Rate setup for the relevant Scenario, Year, Currency, and Currency Type.

COA Segment Combination Validation fail in Data Load Rules

• The uploaded file contains a combination of COA segment values (e.g., Account, Department, Location) that doesn’t match any valid predefined combinations

• The validation rules or segment hierarchies in Planful reject this combination as invalid

• Review the COA segment validation rules and hierarchy mappings in Planful

• Confirm the uploaded combinations are valid, and active in the configuration

• Correct the invalid combinations in your upload file before reloading