As of April 2026, most Old Aggregate Tables have been migrated in the backend. However, some Old Aggregate Tables could not be migrated smoothly due to unreasonable configurations.

The New Aggregate Table now covers the business scenarios supported by the Old Aggregate Tables. To avoid feature redundancy and prevent Old Aggregate Tables from blocking the expansion of new features, Jodoo will deprecate the Old Aggregate Table feature.

After the feature is deprecated, all remaining Old Aggregate Tables will be converted to New Aggregate Tables by default. Existing business processes that reference Old Aggregate Tables may be affected. Administrators are advised to manually adjust and upgrade Old Aggregate Tables to New Aggregate Tables before the deadline.

Free and trial plans: The evening of May 31, 2026
Paid plans: The evening of June 30, 2026

After Old Aggregate Tables are deprecated, any remaining Old Aggregate Tables under an app will be automatically converted to New Aggregate Tables. Details are as follows:

Unreasonable configurations in Old Aggregate Tables will be highlighted in red as errors in New Aggregate Tables.
If an Old Aggregate Table is referenced in a form or dashboard, you need to resolve the highlighted errors in the upgraded New Aggregate Table before the configurations in the form or dashboard can take effect again.

Manual Adjustment and Upgrade

To ensure that your business is not affected, we recommend that you check the Old Aggregate Tables in your workspace and manually upgrade them based on actual usage.

The manual adjustment and upgrade process is as follows.

Step 1 Checking Old Aggregate Tables

After entering the Workspace, click Click to Open the Troubleshooting Assistant at the top of the Workspace to access the Old Aggregate Table Troubleshooting Assistant.

Note:

The Troubleshooting Assistant is available only to paid-plan users who still have Old Aggregate Tables.

2. After entering the Old Aggregate Table Troubleshooting Assistant, you can also use the following methods to assist your judgment:

If errors already exist in the row headers and metrics of an Aggregate Table but do not affect actual business use, the Aggregate Table is likely deprecated or unused.
If the reference details of an Aggregate Table are empty, the Aggregate Table is likely deprecated or unused.

3. Continue checking the upgrade error information for the Aggregate Tables. You can view error information directly on the page, or click Export Error Information to download and view it.

4. After checking the Old Aggregate Tables, you can handle them as follows:

Usage Type	Recommended Action
In use	Check for unreasonable configurations, then adjust and upgrade it to a New Aggregate Table. For detailed steps, see Step 2, Adjusting and Upgrading Old Aggregate Tables.
Deprecated or unused	After confirming that it is no longer used, you can choose any of the following actions: 1. Delete the Old Aggregate Table. 2. Convert it to a New Aggregate Table by clicking Upgrade > Ignore and Upgrade. The configuration will contain errors. 3. Wait for the feature to be deprecated, after which it will be automatically converted to a New Aggregate Table. The configuration will contain errors.

Step 2 Adjusting and Upgrading Old Aggregate Tables

If you need to manually adjust and upgrade an Old Aggregate Table, you can use either of the following paths. For details, see Old Aggregate Table Upgrade Assistant.

1. Upgrade from within the Aggregate Table

Go to the settings page of the Old Aggregate Table that needs to be adjusted and upgraded. Click Upgrade. After locating the cause of the upgrade error, you can either adjust the configuration first and then upgrade, or click Ignore and Upgrade to convert it to a New Aggregate Table first and then adjust the configuration.

2. Upgrade through the Upgrade Assistant

Go to App Management > Advanced Features > Aggregate Tables, and click Upgrade Assistant on the right side of the Old Aggregate Table. On the Upgrade Assistant settings page, select the Old Aggregate Table that needs to be upgraded, and click OK. After locating the cause of the upgrade error, you can either adjust the configurati on first and then upgrade, or click Ignore and Upgrade to convert it to a New Aggregate Table first and then adjust the configuration.

Adjustment Methods for Upgrade Failures

Based on the error type and the corresponding solution, you can adjust the Old Aggregate Table and then upgrade it, or click Ignore and Upgrade to convert it to a New Aggregate Table first and then adjust the configuration.

Code	Error Type	Description	Recommended Action
101	Data source contains deleted forms	A form referenced in the data source has been deleted.	Delete or modify the form that causes the error.
401	Filter conditions contain deleted fields	A deleted field is referenced in a filter condition.	Delete or modify the filter condition that causes the error.
402	Dimensions contain deleted fields	A deleted field is referenced in a dimension.	Delete or modify the dimension that causes the error.
403	Metrics contain deleted fields	A deleted field is referenced in a metric.	Delete or modify the metric that causes the error.
201	Filter condition contains “array equals”	The equals condition is configured for Checkbox, Multi Select, Members, or Departments fields in the filter conditions. This causes an error because using equals for array-type fields is not standardized, and the New Aggregate Table no longer supports this usage.	Delete the condition, or change it to contains any or contains all.
301	Dimensions contain multiple subforms under the same form	In the dimension or field connection configuration, subfields in the same column can only come from one subform.	1. If dimensions from other subforms are unnecessary, delete them directly. 2. If data from other subforms needs to be calculated: add the subform as a data source in the New Aggregate Table, or create a new Aggregate Table to aggregate data from that subform.
501	When aggregating a main field dimension, metrics contain both main fields and subfields	If only a main field of a form is needed in dimension building, an error occurs when the metrics reference both the main field and subfields of the same form.	1. If the corresponding subfield metric is unnecessary, delete it directly. 2. If the corresponding subfield metric is necessary: add the subform as a data source in the New Aggregate Table, or create a new Aggregate Table to aggregate data from that subform.
502/601	Metrics contain subfields that are not from a data source	Fields referenced in metrics can only come from forms or subforms in the data sources. An error occurs if fields from other subforms are referenced.	1. If the corresponding subfield metric is unnecessary, delete it directly. 2. If the corresponding subfield metric is necessary: add the subform as a data source in the New Aggregate Table, or create a new Aggregate Table to aggregate data from that subform.
701	When aggregating a subfield dimension, metrics contain main fields	If a subform field of a form is used in dimension building, the corresponding subform must be selected in Data Source. In this case, metrics can use only subfields from that subform. An error occurs if a main field of the form is referenced.	1. If the corresponding main field metric is unnecessary, delete it directly. 2. If the corresponding main field metric is necessary, consider one of the following three methods: use subfield aggregation to achieve the effect of aggregating the main field; add the form without the subform as a data source; or create a new Aggregate Table to calculate the main field metric.
801	Filter conditions contain subfields that are not from a data source	Subfields used in Filter Conditions can only come from the subform selected in Data Source. An error occurs if they come from another subform.	1. If the corresponding filter condition is unnecessary, delete it directly. 2. If the filter condition is necessary: add the subform as a data source in the New Aggregate Table; or use a formula in the original form to convert the subfield value into a main field, and then filter this main field in the Aggregate Table.
901	Incorrect metric configuration	An error occurs when the metric formula configuration does not meet the required rules.	Modify the metric formula that causes the error.
902	Incorrect validation condition configuration	An error occurs when the validation condition formula configuration does not meet the required rules.	Modify the validation condition formula that causes the error.
1501	Data source contains unreferenced forms	A form has been added to the data sources, but fields from this form are not referenced in any metric.	Delete the redundant data source, or configure the required metrics based on this data source.

Upgrade Example

Error 701 is relatively complex to handle, so this section explains this error separately. The following inventory statistics example demonstrates how to adjust and upgrade this type of error.

Error Cause Analysis

Example

Old Aggregate Tables did not restrict the field connection rules, row headers, or subfields used in metrics. As a result, calculation results could be incorrect under certain special configurations. The New Aggregate Table adds the following restriction: When the data source is a form plus a subform, dimensions can use main fields or subfields from the selected subform, while metric formulas can reference only Number-type subfields from the selected subform. If an Old Aggregate Table does not comply with this rule during upgrade, Error 701 occurs.

Inventory statistics scenario

Step 1 Checking Whether the Aggregate Table Is in Use

Query the Old Aggregate Table usage details and confirm that the status of this Aggregate Table is In use.
View the Aggregate Table reference details. You can see that it is referenced by a form, and you can determine that the business process using this table is operating normally.

Based on the query and reference details, this Aggregate Table is in use and needs to be manually adjusted and upgraded.

Step 2 Upgrading and Obtaining Error Information

1.Upgrading the Old Aggregate Table

1) Click Upgrade. The error information returned is 701.

2.Locating the Specific Cause of the Error

1) Review the Old Aggregate Table configuration.

After review, the configuration of the Old Aggregate Table is as follows:

Source Form	Fields Referenced by Row Headers	Fields Referenced by Metrics
Inbound Order	Product No. in Inbound Details 1	Inventory Quantity
Outbound Order	Product No. in Outbound Details 1	Inbound Quantity in Inbound Details 1 (subfield); Inbound Quantity in Outbound Details 1 (subfield); Inbound Year Marker Count; Inbound Year Marker Count (main field); Total Inbound Amount; Total Inbound Amount (main field)

2) Locate the specific cause of the error.

The row header uses a subfield from Inbound Order. Therefore, in the New Aggregate Table, you can directly select the subform Inbound Details 1 in the data sources. In this case, metrics can use only fields from the subform Inbound Details 1, and cannot use main fields.
After checking, the metrics Inbound Year Marker Count and Total Inbound Amount reference the main fields from Inbound Order, so these two fields need to be adjusted.

Step 3 Manually Adjusting and Upgrading to a New Aggregate Table

According to the help documentation, Error 701 can be handled in multiple ways. The following section demonstrates four methods. When performing the actual operation, users should determine which method applies based on their business scenario. In this example, Method 1 and Method 2 are more suitable.

Method	Adjustment	Example
Method 1	If the corresponding main field metric Inbound Year Marker Count is unnecessary, delete it directly.	Delete the unnecessary metric and then upgrade.
Method 2	In the Old Aggregate Table, convert the formula of Total Inbound Amount into aggregation of the subfield Inbound Details 1.Inbound Amount, and then click Upgrade.	Convert the metric formula to reference the corresponding subfield before upgrading.
Method 3	Click Ignore and Upgrade to convert the table to a New Aggregate Table. The system automatically adds Inbound Order as a data source without a subform. You then need to manually complete the dimensions for Inbound Order as follows: 1. Click Configure Data Source Forms, and add the source form as Inbound Order > Inbound Details 1. 2. Click Incomplete Dimension Configuration, and set the dimension under Inbound Order.Inbound Details 1 to Inbound Details 1.Product No.	Complete the data source and dimension configuration after upgrading.
Method 4	Create a new Aggregate Table specifically to calculate Inbound Year Marker Count and Total Inbound Amount. Then delete Inbound Year Marker Count and Total Inbound Amount from the original Old Aggregate Table, and upgrade it to a New Aggregate Table.	Build a new Aggregate Table, then delete the metrics from the Old Aggregate Table before upgrading.