Error when creating field | Only Admin access

English Language - Forum
1

“Database failure. Please refer to suitecrm.log for details.”

Version 7.10.33

Sugar Version 6.5.25 (Build 344)

QRR has not helped.

I can find how this may be resolved if you’re someone with direct coding access, but I’m an admin with no coding access as I didn’t create the SuiteCRM my work currently uses.

Because the nature of our modules is specific to the organisation, I’ve been adding in fields directly to the module in Studio. The module I am current working on has given me this error when I’ve tried to create more fields (currently there are 173 fields).

I need to find out if there’s a possible way for me to fix this as an admin only?

Additionally, our CRM doesn’t allow mass adding or deleting of fields. I’ve had to add these fields 1 by 1. I’d like to avoid undoing my work.

Thank you.

2

Did you refer to the log?
For the version 7.x these apply:

If you could check your suitecrm.log what’s happening around the module / around the time you’ve received the error and post part of the log file here, that will help.

Yes, that’s true.
It is possible to “create” fields via PHP files as well but then you don’t have the UI anymore.
(it’s not a feature I know from other CRM systems though - probably the thought goes like: That’s a one time thing, very customized and therefore manual is fine).

You’re working directly in the live system? Not on a backup / dev environment?
Technically that’s possible, just not necessarily advisable :wink:

3

Thank you so much for your reply!

I’ve checked the logs and received the following:

Fri Aug 1 06:51:27 2025 [4181142][5efa70ac-9ec4-2361-2242-686c73b34a76][FATAL] Cannot create column Query Failed: ALTER TABLE name_name_office_inspection_cstm add COLUMN fwup_action38_c varchar(255) NULL : MySQL error 1118: Row size too large. The maximum row size for the used table type, not counting BLOBs, is 65535. This includes storage overhead, check the manual. You have to change some columns to TEXT or BLOBs

I’ve attempted to change some textfields to size 50 from 255, but it hasn’t gotten me very far.

The purpose of this module is a checklist for an office inspection with over 100+ items needing to be checked off. Alongside the items needing to be checked off, a comment box is needed.

I don’t technically have access to a dev environment as far as I know, I’ve been assigned to set up modules for our specific branch of our organisation and really just have admin access. Unless there’s something I’m not aware of/doing incorrectly where I should be able to utilise a dev environment!

Would love to know what you think! Thanks!

4

Yes, I’ve seen this before :frowning:

You can switch the DB types from VARCHAR to TEXT (on the DB, not the CRM) in order to reduce allocated space.
TEXT data type is stored off-page and doesn’t count against the InnoDB pages / limits.

Your approach with changing the size from 255 to 50 is working to some extend. If you do this from the Studio, this will be changed in the DB as well.
You’ll still have to calculate the maximums carefully.

Your comment - if you used a text area - should be fine, the CRM assigns the type TEXT to a text area.

Another easy fix is, to simply split this module up into two:
Checkbox Group 1
Checkbox Group 2
and distribute the fields accordingly.

I assume, if the team has to fill out 100 fields, efficiency isn’t the highest priority and making it two separate modules could be acceptable :wink:

2 Likes
5