What Happens When an Upgrade Fails?
When you attempt to upgrade a legacy aggregate table using the Upgrade Assistant, the system automatically validates all configurations. In rare cases, certain configurations are not compatible with the new aggregate table format, and the upgrade will fail with an error code.
When this happens, don't worry—you have two options:
Modify the legacy table and re-attempt the upgrade (for some error types).
Generate a new aggregate table manually and adjust its configuration to match your needs.
This guide walks you through each error type and provides clear solutions.
Detailed Solutions by Error Code
Error 101: Data source contains deleted forms
What's happening: One or more tables in your aggregate table's data sources have been deleted from your app.
How to fix it:
Click Generate a new aggregate table from the old to create a new version.
In the new table's configuration, remove the deleted table from the Data Sources section.
If you need to replace it with a different table, delete the old one first, then add the new table.
Important Note:
Do not modify the data sources directly in the legacy table, as this may cause references in forms and dashboards to break after the upgrade.
Error 201: The filter condition for an array-type field is set to "equals"
What's happening: Your filter condition uses the "equals" operator on array-type fields (like Checkbox, Multi Select, Members, or Departments). This syntax is no longer supported in the new format.
How to fix it (choose one):
Option 1 - Modify and re-upgrade:
In the legacy aggregate table, find the problematic filter condition.
Change the operator from "equals" to either "contains any" or "contains all".
Re-attempt the upgrade.
Option 2 - Generate new and adjust:
Click Generate a new aggregate table from the old.
In the new table, update the filter condition to use "contains any" or "contains all".
Error 301: The dimension contains multiple subforms under the same form
What's happening: Your dimension configuration references more than one subform from the same table. The new format only allows one subform per table in dimensions.
How to fix it:
Click Generate a new aggregate table from the old.
Review the dimensions that reference multiple subforms.
For each dimension:
If it's not essential, delete it.
If you need to analyze data from multiple subforms, create a separate aggregate table for each subform.
Error 401: The filter conditions contain deleted fields
What's happening: A field that your aggregate table references (in filters, dimensions, or metrics) has been deleted from the source table.
How to fix it:
Click Generate a new aggregate table from the old.
Identify the deleted field in the configuration.
Either remove it or replace it with an active field.
Errors 402, 403, 601, 702, 902: Configuration Issues
What's happening: The system detected a configuration error or inconsistency in your aggregate table.
How to fix it:
Go back to your legacy aggregate table.
Click Save to re-save the entire table (this often resolves minor inconsistencies).
Attempt the upgrade again.
If the issue persists, click Generate a new aggregate table from the old and manually reconfigure the table from scratch.
Error 501: When aggregating the main field dimension, both main and subfields are included in the metric
What's happening: Your dimension uses a main field from a table, but your metrics reference both the main field and subfields from that same table. This creates ambiguity in how data should be aggregated.
How to fix it:
Click Generate a new aggregate table from the old.
Review your metrics and adjust them to use only one type of field (either main fields or subfields, not both).
Example: If your metric references a main field that is actually a summary of subfield data, replace the main field reference with the corresponding subfield.
Error 502: The metric contains subfields that are not from a data source
What's happening: Your metric uses a subfield, but that subfield's table is not included in your data sources, or the wrong subform is selected.
How to fix it:
Click Generate a new aggregate table from the old.
Ensure that the Data Sources section includes the correct table and subform.
Update the metric to reference only fields from the selected data sources.
Error 801: The filter condition contains fields of subforms that are not the data source
What's happening: Your filter condition references a subfield, but the corresponding subform is not properly configured in your data sources.
How to fix it (choose one):
Option 1 - Remove the filter:
If the filter is not essential, delete it entirely.
Option 2 - Align data sources and filters:
Click Generate a new aggregate table from the old.
Ensure your Data Sources include the correct subform.
Update the filter to reference only fields from the selected data sources.
Option 3 - Use a main field instead:
In your source table, create a formula field that converts the subfield value to a main field value.
Update the filter condition to use this new main field.
Error 901: Incorrect metric configuration
What's happening: The formula in your metric or validation condition has syntax errors or references invalid fields.
How to fix it (choose one):
Option 1 - Fix in the new table:
Click Generate a new aggregate table from the old.
Edit the problematic formula to correct the syntax.
Option 2 - Fix in the legacy table:
In your legacy aggregate table, review the metric or validation formula.
Correct any syntax errors or invalid field references.
Re-attempt the upgrade.
Error 1501: There are data sources with unreferenced forms
What's happening: You've added a table to your data sources, but none of your metrics actually use fields from that table.
How to fix it:
Click Generate a new aggregate table from the old.
Either:
Remove the unused table from data sources, or
Add metrics that reference fields from that table.
Error 902: Validation condition configuration error
What's happening: The system encountered an error while saving your aggregate table configuration, preventing a clean upgrade.
How to fix it:
Go back to your legacy aggregate table.
Click Save to re-save the table.
Attempt the upgrade again.