SugarCRM 5.2i doesn't import custom fields

[ryan.mcgarrie]

Hi,

We've started to move alot of our data accross to a new implementation of SugarCRM 5.2j.
Unfortunately, it doesn't import data into custom fields that I created in Studio - for Accounts.

I cant seem to find a known bug (past v5.2a) is anyone experiencing the same problem?

Any help would be appreciated. PLEASE!!!!

Thanks,

[salesagility]

When you created the custom field did you mark as being available for import?

[esilverberg]

I am seeing this behaviour. My fields are marked as importable. Sugar 5.2.0j flat out refuses to import custom fields, even though I can map them just fine.

[salesagility]

Are you getting any error messages ... what are they?

what versions of webserver, operating system, database and php are you running?

[esilverberg]

I realized the issue.

When I created a URL field, sugar gave it a default size of 25. That limitation was expressed in the database and never exposed in the import UI. When it tried to execute the INSERT statement for leads_cstm, mysql failed with a "data too large for field" error, but sugar silently swallowed this error and went along creating records. A failure for one custom field resulted in no custom fields being stored, because all the custom fields are stored in one INSERT statement.

The solution was to go back and enlarge the field size for those custom fields to 255.

Sugar should not be hiding these kinds of mysql errors - the whole insert should have failed and it should have told me why.

[Captivea]

Check the datatable as well
Sugar 5.5 can break the import functionnality if you first created some required fields in the studio (it creates a not null column as well in the DB) and then delete the column from the studio (it doesn't delete the column in the db, and so MySQL can't insert new rows)

You have to manually delete the column before being able to import any data