Custom Fields not saving Sugar 5.0.0b

[Danielg42]

Hey guys!
I've created around 30 custom fields for one module in my sugar installation. They all are properly laid out an allow you to enter information, but when I save the entry, any data in a custom field is not saved.
The data in the original fields is fine and editable, but my custom fields are not saving. The module_cstm table in the database exists, with all the fields, but no rows with the new information are being added.

Any ideas?
If someone could refer me to the php file that actually does the sql query, so I could further investigate, I'd be really grateful.

[Angel]

Try enabling debug logging.

Chances are that the query for saving the data is either malformed or references a field that doesn't exist. I've seen the latter occur if custom fields are added/deleted or the database is moved from one location to another.

[Danielg42]

How would I go about enabling debug logging? I have developer mode on.. is that enough?
Disregard... I got it now!

Ok, so it's enabled, but I don't see anything wrong with the queries, they simply leave out any custom field data.
The original fields are all updated, but the custom ones aren't even mentioned in the log. Any other places to check besides sugarcrm.log?

[julian]

To truly dump all the queries being sent out, you'll need to enable "slow query logging" (and set the threshold to 0ms).

To enable slow query logging, visit the Admin area (by clicking the link in the top-right corner), then click System Settings.

Toward the bottom of the screen, you'll find a checkbox for "Log slow queries" and a textbox for "Slow query time threshold" -- check the box and enter 0 as the threshold, then save. All queries should then be dumped to sugarcrm.log. Look for the normal INSERT INTO module ... that's working-- a second INSERT INTO module_cstm should be attempted shortly thereafter.

If all else fails, you can check the save() method in ./data/SugarBean.php.

[wjohnson]

How would I go about enabling debug logging? I have developer mode on.. is that enough?
Disregard... I got it now!

Ok, so it's enabled, but I don't see anything wrong with the queries, they simply leave out any custom field data.
The original fields are all updated, but the custom ones aren't even mentioned in the log. Any other places to check besides sugarcrm.log?

We had a problem like this previously and the solution was to disable strict mode in MySQL. I don't know if Sugar still doesn't work with that but it would be nice some day if they did so it could share a server with financial and other sorts of apps that require that.

[dasbandana1983]

Hi,
I am having the same problem. I am using the SugarCE-Full-5.0.0e-Ja. I have created the a custom module in which i have created four custom fields
1. Company Name(Related to Accounts).
2. Contact Person(Related to Contacts).
3. Date of Entry(Date).
4. Title(Text Field).

When I am saving these data the two relate fields are not getting saved in the table but the account_id and contact_id is getting saved. I want to save the companyname and contactperson in database so as to fetch the data in the list view.All other custom field data are being saved except the two custom 'relate' fields. Please suggest what to do.

[jbmdn]

I think I'm having the same problem here.. 5.0.0e
Did anyone fix it or any suggestions?

Thanks jbmdn

[andopes]

Hi, all.

Make sure the Provide existing user can alter table in the database used by Sugar.
Check his privileges using the phpMyAdmin.

Cheers

[gguillote]

Hi,
I've the same problem. I'm using SugaCrm CE 5.00f.
When I try to save relate fields it doesn't save the text field related to the selected option.
For example, there is a module called "City" and a related field in Accounts module. When I choose a city, Sugar saves the Id but not the text.
Any suggestions?

Thanks in advance.

[andopes]

Hi all

If you have access to the code edit the file modules/DynamicFields/DynamicFIeld.php
Edit the function save to print in a file (or in the screen) the query for the update/insert into cstm_table.
try to run this query in the phpMyAdmin and checks if it has any kind of error.
This can guide you to the fix.
Probably it is a custom field metadata issue.

Cheers