The Health Check wizard must be run when upgrading in order to evaluate your instance’s ability to move to the target version. During the health check, various types of issues may be detected which can affect your ability to upgrade. This article will cover how to resolve a “badVardefsTableName” error reported by the health check
This error generates an output similar to the following in health check:
The generated error message will help determine the contents of the file causing the health check error. To address this issue, the code-level customization will need to be edited from Sugar before proceeding with the upgrade.
Breakdown of health check error:
- The file causing the error can be found in
- The health check detects an issue with the table name in the file.
In this example, the table was renamed
accounts_example in the file system, but this table name does not exist in the database.
In order to resolve the health check error, change the table name to
accounts as follows:
Another common cause of this error is that the table name in the vardefs will contain uppercase letters but the value is expected to be all lowercase.
Once the necessary change has been made, please navigate to Admin > Repair and perform a “Quick Repair and Rebuild” to ensure that the changes are synced between the application and database. Then, perform the health check again to confirm that the error is no longer reported.