Background
In April 2026, Jodoo completed an automatic upgrade that is compatible with Old Aggregate Tables.
From May 2026 to June 2026, Jodoo sent multiple rounds of deprecation notices for the old feature through in-app messages, the Workspace homepage, service groups, phone calls, and other channels. Jodoo also assisted users in manually upgrading Old Aggregate Tables with incorrect configurations.
On the evening of June 30, 2026, Jodoo deprecated the Old Aggregate Table feature. Any Old Aggregate Tables that had not been upgraded by that time were automatically converted to New Aggregate Tables.
How to Manually Configure the Old Aggregate Table?
If an Old Aggregate Table was not manually adjusted and upgraded before the deadline, 24:00 on June 30, 2026, or if a user ignored the errors and manually upgraded an Old Aggregate Table, configuration errors may occur after the table is automatically converted to a New Aggregate Table if it contains incorrect configurations. Users need to manually adjust the configurations and complete the calculation before the Aggregate Table can be referenced normally.The manual adjustment process is as follows.
Viewing Error Information of Old Aggregate Tables
On the Aggregate Table edit page, click View Old Aggregate Table Configuration.
On the Old Aggregate Table configuration page, click View Upgrade Error to locate the error type. Then adjust the configuration according to the error information and the methods provided before.
Adjustment Methods for Upgrade Failures
Based on the error type and the corresponding solution, adjust the configuration in the New Aggregate Table.
Code | Error Type | Example / Description | Recommended Action |
101 | Data source contains deleted forms |
 | Delete or modify the form that causes the error. |
401 | Filter conditions contain deleted fields |
| Delete or modify the filter condition that causes the error. |
402 | Dimensions contain deleted fields |
| Delete or modify the dimension that causes the error. |
403 | Metrics contain deleted fields |
| 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 dimension or join 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. |
Handling Error 701
Error 701 is relatively complex to handle, so this section explains this error separately. The following inventory statistics example demonstrates how to manually adjust 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. | 
|
1.Reviewing 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 |
|
| Inventory Quantity
Inbound Year Marker Count
Total Inbound Amount
|
2. Locating 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 main fields from Inbound Order, so these two fields need to be adjusted.
3.Manually Adjusting the New Aggregate Table
According to the help documentation, Error 701 can be handled in multiple ways. The following section demonstrates five methods. When performing the actual operation, users should determine which method applies based on their business scenario. In this example, Method 1 and Method 3 are more suitable.
Method | Adjustment |
Method 1 | If the corresponding main field metric Inbound Year Marker Count is unnecessary, delete it directly.  |
Method 2 | If the corresponding main field metric Inbound Year Marker Count is necessary, make the following adjustments: 1. In the Inbound Details 1 subform of Inbound Order, add an auxiliary field named Inbound Year Marker Count. Set the formula to equal Inbound Year Marker Count.  2. In Data Management of Inbound Order, use Batch Edit to set Inbound Details 1.Inbound Year Marker Count to the formula value of Inbound Year Marker Count.  3. Return to the Aggregate Table. Change the field referenced by the metric Inbound Year Marker Count to Inbound Details 1.Inbound Year Marker Count, and change the aggregation method to AVG.  |
Method 3 | In the New Aggregate Table, convert the formula of Total Inbound Amount into aggregation of the subfield Inbound Details 1.Inbound Amount.  |
Method 4 | In the New Aggregate Table, add the corresponding subform as a data source:
|
Method 5 | 1. Create a new Aggregate Table specifically to calculate Inbound Year Marker Count and Total Inbound Amount.  2. Delete the metrics Inbound Year Marker Count and Total Inbound Amount from the original Aggregate Table.  |
Handling Error 801
1. Reviewing the Old Aggregate Table Configuration
After review, the configuration of the Old Aggregate Table is as follows:
Source Form | Filter Condition | Fields Referenced by Row Headers | Fields Referenced by Metrics |
Reimbursement Application | Invoice Recognition List.Final-Level Subject Code equals any of 1156 |
| Expense Allocation Details.Travel Expenses |
2. Locating the Specific Cause of the Error
The row headers and metrics reference subfields from the Expense Allocation Details subform. Since the New Aggregate Table can use only main fields or subfields from the subform specified in the data source, filter conditions can only reference subfields from the Expense Allocation Details subform.
After checking, the filter condition references a subfield from Invoice Recognition List, so the filter condition needs to be adjusted.
3. Manually Adjusting the New Aggregate Table
According to the help documentation, Error 801 can be handled in two ways. The following section demonstrates how to modify the configuration without deleting the filter condition. When performing the actual operation, users should determine which method applies based on their business scenario.
Step | Adjustment |
Step 1 | In the Reimbursement Request form, add a main form field named Detailed GL Account Code Contains 1156, and use a formula to check whether the subform field meets the condition.  |
Step 2 | Go to Manage Data, click Filter, and set the filter condition as follows:
|
Step 3 | Click Batch Actions > Batch Edit > Filtered Data, and configure the following settings:
 |
Step 4 | Go to the New Aggregate Table, and change the filter condition to the main form field:
|
Special Compatibility Notes
After the upgrade is completed, the following situations may occur. You can adjust the related configurations based on your actual needs.
Formula Simplification
In Legacy Aggregate Tables, some metric formulas were configured by adding or subtracting unnecessary variables to meet configuration requirements. When upgraded to New Aggregate Tables, these metric formulas are automatically simplified. The simplified expression may be 0 * COUNT(x). This does not affect the use of the metric. You can keep this expression or delete it manually.
Invalid Variables in Validation Rules
In data submission validation conditions of Legacy Aggregate Tables, invalid variables refer to metrics that were originally used in validation formulas but became invalid after the corresponding metrics were deleted.
During the upgrade, the original validation conditions are retained, and the invalid variables in them are replaced with 0.
Upgrade-Compatible Versions
A small number of legacy tables with configurations that exceed current limits (e.g., too many source tables, dimensions, or filter conditions) will be converted into an "Upgrade-Compatible Version." This special version ensures the table continues to function with its legacy logic. However, if you copy this app or table, the new copy will be a standard aggregate table and will require manual configuration to work correctly.
Note: When an Aggregate Table is copied within an app, when an app is copied within an enterprise, or when an app is installed through an external link, the copied Aggregate Table will be a regular Aggregate Table. You need to modify it to the correct configuration before performing a full calculation.
Upgrade-Compatible Metrics
If the system detects redundant data source tables during the upgrade, it may add an "Upgrade-Compatible Metric" to assist the process. This metric does not affect the table’s normal use, and you can safely delete it yourself after the upgrade is complete.
