check the DB table fields_meta_data and the directory custom/Extension/modules//Ext/Vardefs/ If there are files in the latter that resemble: sugarfield__c.php, that are not represented in the former, then removing them should clear up the issue. (from pmcqueen)
Tried to solve the same situation, find the sugarfieldxxxx.php file, and deleted. Quick repair and rebuild, and nothing happens: null is still there. Additionally, when trying to create a record, I get a database error in sugarcrm.log. This is the offending portion of the sql: SET name = 'Opportunity name' , date_modified='.........................................probability=20,[B]=NULL[/B] There is a field name missing, but I noted, and don't know if this is relevant, that SET is made over not custom fields (there are no '_c' fields in the query). Additionally supposing (not custom) vardefs.php is modifed by hand, is expected that when a repair and rebuild is executed, sugar realizes the situation and create the missing fields in the database... and in this case, fields_meta_data table does not make the difference. Please tell me if I am wrong.. There must be another file in some place causing this.. (from hdanielb)
Tried to solve the same situation, find the sugarfieldxxxx.php file, and deleted. Quick repair and rebuild, and nothing happens: null is still there. Additionally, when trying to create a record, I get a database error in sugarcrm.log. This is the offending portion of the sql: SET name = 'Opportunity name' , date_modified='.........................................probability=20,[B]=NULL[/B] There is a field name missing, but I noted, and don't know if this is relevant, that SET is made over not custom fields (there are no '_c' fields in the query). Additionally supposing (not custom) vardefs.php is modifed by hand, is expected that when a repair and rebuild is executed, sugar realizes the situation and create the missing fields in the database... and in this case, fields_meta_data table does not make the difference. Please tell me if I am wrong.. There must be another file in some place causing this.. (from hdanielb)
