Email field class is limiting characters to 32. How to increase the max length?

[ngriffiths]

We have a field class on our table that is a type of 'email'.   How do I increase the max length the field will accept?   I went into the field class table and set the length value on email to 200.   I have also tried an attribute max_length=200; but it still is cutting emails to 32 characters.

[ngriffiths · Accepted solution]

Hi all,

Here is the resolution to this:

1. Go to "sys_glide_object.list"
2. Find and open "email"
3. Enter "100" in the "length" field and save (or update).
4. Now go to the form you want that field on.
5. Add a NEW email field! You can use the same name if you want, but more than likely the actual name will change in the background.
6. Delete or move the first email field.

If you only have a few records, you can update the data manually or if you have a bunch, then you can export the data and then import the data to the correct field.

[chris_lo]

This is not the correct way to go about this. Customers should never make any changes off of the sys_glide_object table unless instructed by SNOW. The email field is a simple string type field so the simplest way to go about this would be to go ahead and then just change the max length from the dictionary entry of the respective field and then running the following commands from scripts background to clear out table descriptor cache.

gs.invalidateCache();

gs.clearCache();

By making this change from the Field Class table it is a global change that will populate across all email fields in the system but we have seen data loss around make such changes to this table as Sergiu pointed out the DB changes may not be in effect. Also creating the field with the same name will not be possible as the platform would reject it since the column already exists. You would want to create a new column with a different name and then write a script to move the data from the old field to the new field and then effectively drop the old field.

If you have any questions or concerns please raise a ticket with our support team.

Chris Lo

Sr. Technical Support Engineer

[akeppel]

Just thought I'd throw my finding out here as well.

I had this same issue but my sys_user.email field was already set to a max length of 255.   The cause of my issue was actually the field definition in the ldap import table (ldap_import).   The max_length of the ldap_import.u_email field (which was probably auto-created many moons ago during our initial implementation) was set to 40.   Our eMail addresses were being clipped during the actual import from AD, not the insert or update to the sys_user table.

Hope that helps some.