Details about this thread
  • State Not Answered
  • Replies 6 replies
  • Subscribers 321 subscribers
  • Views 1774 views
  • Users 0 members are here

Issue with fields_meta_data.id_c after upgrading to 11.0.3

Freddy Jreisat

I completed an upgrade on our sandbox instance from SugarEnt 9.0.0 > 11.0.3.

After I was finished with the upgrade to 11.0.3, I ran a QRR and there was some mismatches with the database. I executed all of the SQL commands except one, which is trying to alter the fields_meta_data.id_c field to 36 (CHAR) field type. Evidently, many years ago someone must have done a customization on this SugarCRM installation to change the properties of fields_meta_data.id_c column. It is 255len (VARCHAR) field, and instead of having a 36-char key as the value, in my fields_meta_data table, the id field is just a copy of the field name (see img below):

Over 40 records in the fields_meta_data table have an existing id that is longer than 36 characters. My question is simply: what should I do to rectify this? I reached out to Sugar Support and they directed me here, as they say this must have been caused by a past customization. Willl greatly appreciate any help. Thank you.

Parents
  • 0

    Until a very recent release, the ID of the fields_meta_data table was 255 characters. The change to 36 characters occurs as part of the upgrade process. This is not caused by previous customization.

  • 0 in reply to Jeff Bickart

    To add to 's response, they didn't just change the size, they changed the ID.
    It used to be a concatenation of module name and field name, and now it's a UUID, however they did not convert the old records to UUID, they have the old id format. 
    So the table now has a mix of UUID and strings in the ID column, which looks a bit messy in my opinion.

  • 0 in reply to Francesca Shiekh

    Well, my case rep still won't help. Could one of you knowledgeable people let me know how I should rectify this? Should I just truncate the required number of characters to get it down to 36? Willl there be any consequences for doing so?

  • 0 in reply to Freddy Jreisat

    I did a quick grep on my SugarCRM code to see if the IDs were used anywhere, I did find them in the cache files but nowhere else. So you may be ok updating them.

    If you are going to try it, I would suggest you make a backup of your code and DB first.

    Then I would try to update those problematic records to have UUID() or truncate the id if you don't get any duplicates, and QRR. 
    Then see what you can see... it's a bit of a gamble (hence the backup) but it might work...

  • 0 in reply to Francesca Shiekh

    Thank you. :) I will try. 

Reply Children
No Data