In adding new custom fields to an existing set, things recently went wrong. New entries were added in the civicrm_custom_field table, but the corresponding columns were not added to that field set's table. This resulted in
DB Error: no such field breaking the UI display of existing cases. Deleting the rows from the custom_field table solved the errors so that existing cases can be viewed.
Now new cases cannot be created. When the new case form is submitted the case gets partially added to the db (but is not visible via the UI) and a blank error screen with message
DB Constraint Violation - case_type_id should possibly be marked as mandatory for Case,get API. If so, please raise a bug report. appears. Creating a new case (or trying to) adds 83000 new lines to the log file and near the top of that entry is
[nativecode=1054 ** Unknown column 'a_to_civicrm_value_special_case_fields_8._name_of_deleted_field_157' in 'field list']. That seems confusing since "a_to_" is not actually part of the table's name, and "_name_of_deleted_field_157" isn't in the civicrm_custom_field table. Are custom fields recorded/stored anywhere aside from civicrm_custom_field and the fieldset they're contained by?
Also, the field and case id's seem to have their incrementing messed up... the id#s appear to increment by 1 but there are several numbers skipped. Is that a problem? With the fields I deleted the row and column back to the last increment, 148, but when adding a new field its id was 155. Can missing id's (149-154 in this case) be problematic?
Is there anything you can suggest or point me towards in getting this working?
- 131 rows in civicrm_custom_field table
- CiviCRM 5.13.4