Troubleshooting: calculated fields causing group errors

Note: The system administrator with the appropriate role can access these features.

Problem:

There is a limit to the number of calculated fields that can be added. If that limit is exceeded, groups fail to load. The limit is based upon a maximum number of 32 stored procedures, functions (calculated fields), triggers, or views, so the actual limit can be different per implementation and entity or table.

Groups fail to load with the following error:

Error: Cannot display group “<group name>”.
Error Code: 0x80040E14 Maximum stored procedure, function, trigger or view nesting level exceeded (limit 32)

Scenarios:

Scenario 1: After adding a calculated field with an aggregate or function, other than concatenation, groups fail to load.

Scenario 2: After adding a calculated field with an aggregate or function, other than concatenation, and building and deploying the Web Client, groups fail to load.

Solution:

Delete the calculated field in Application Architect. For steps see Deleting Calculated Fields in the Application Architect help.

Note: Deleting a calculated field from Query Builder deletes the calculated field from the CalculatedFieldData table, but do not delete the computed column from the database or property from the entity. To delete the calculated field from all three locations it must be deleted in Application Architect. The group errors continue until it is deleted from all three locations.