Custom Fields in Accounts are not editing, not sure why.

[JoeySperz]

In the accounts section of Sugar, when i click edit, i can type in my custom fields, but when i click save, it does not show up in the account. It is like this for EVERY custom field, including drop downs. I think this happened when i tried to fix a misspelling in the database on one of my custom fields. Is there any way to fix this?

I attempted the repair, and this has been going on for a few weeks, so now i am starting to have data that is not easily editable and becoming irreplaceable.

ANY suggestions would be appreciated. I hope i do not have to recreate the entire database, there was a lot of customization.

[JVWay]

yes, if you've edited the name of a field in the database independently of Sugar you are going to have problems. How will it know what to refer to. I would backup the database. Delete and recreate your custom fields and then run an update query to fix the fields.

[lmason]

Hope this helps somebody -

Problem: editview not saving custom fields. read forum and found different suggestions. The site I'm working on has 60 custom fields in Leads. I tried database repair with no success.

Resolution: Rather than deleting and re-adding all 60 custom fields, I opened each field in Edit Fields (in Studio) and clicked save. By resaving each field definition, Sugar repaired the problem. I don't know which custom field was the problem, but I suspect there was a custom field type mismatch against a database field type.

Environment - TrixBox SE stacker (CentOS Linux 4.5, MySQL version 4.1.20, Intel Xeon), Sugar 5.0 upgrade from 4.5 then 4.5.1

[rbalof]

Hi, I am not using custom fields and still am having problems changing the opportunities fields. I cannot add, remove or do anything with it. any ideas?

[mkazanci]

Hope this helps somebody -

Problem: editview not saving custom fields. read forum and found different suggestions. The site I'm working on has 60 custom fields in Leads. I tried database repair with no success.

Resolution: Rather than deleting and re-adding all 60 custom fields, I opened each field in Edit Fields (in Studio) and clicked save. By resaving each field definition, Sugar repaired the problem. I don't know which custom field was the problem, but I suspect there was a custom field type mismatch against a database field type.

Environment - TrixBox SE stacker (CentOS Linux 4.5, MySQL version 4.1.20, Intel Xeon), Sugar 5.0 upgrade from 4.5 then 4.5.1

We had the same issue and tried this solution. We ended up removing a drop down field created late last night and now we are back in business. Whew!