We have identified a critical regression in SuiteCRM 8.10 regarding how Studio handles edits to core (standard) fields. Please review this advisory before making any configuration changes to your modules.
The Issue
When a standard core field is edited via Studio (for example, marking the “Industry” field as required or updating a label), the system incorrectly injects a source definition into the generated override files.
By incorrectly labelling a core field as a custom field, SuiteCRM attempts to read and write data to the _cstm database table instead of the primary module table. This causes:
Database Errors: SQL failures during record saving or loading.
Data Invisibility: Core data appearing “missing” or blank because the system is querying the wrong table.
System Instability: Any logic hooks or integrations relying on these core fields will fail to function correctly.
Immediate Workaround
If you have already edited a core field and are experiencing these errors, you can manually resolve the issue by following these steps:
Locate the affected override file in: public/legacy/custom/Extension/modules/<Module>/Ext/Vardefs/
Open the PHP file and delete the specific line that sets the source to custom_fields.
Navigate to Administration > Repair and run a Quick Repair and Rebuild.
If prompted at the bottom of the Repair page, execute the SQL scripts to resync the metadata.
Bug Tracking
A resolution is currently being addressed. You can track the progress and view further technical details via the official GitHub link:
