Skip to main content

Troubleshooting Database Column Length Errors When Creating Custom Fields (CRM)

Overview: This guide helps you resolve database column length errors that prevent creating new custom fields in CRM modules.

Symptom / Error

When creating a new custom field, you receive an error such as:

"Error while creating field 'cf_XXXX': The 'vtiger_[module]cf' exceeds maximum column length."

Common variations include:

  • vtiger_leadscf exceeds maximum column length

  • vtiger_accountscf exceeds maximum column length

  • vtiger_contactscf exceeds maximum column length

You may also experience:

  • "Duplicate Field" errors when retrying, even though no field was created

  • Fields appearing to save but not showing in the module layout

Cause

The CRM module has reached its maximum custom field capacity due to database-level limits. Additional causes include:

  • Database schema corruption

  • Excessive deletion and re-creation of fields

  • System misinterpretation of current column limits

Solution

⚠️ Important: This is a backend database issue that requires technical intervention. Do not attempt to create more fields β€” further attempts may worsen the issue.

  1. Stop attempting to create additional fields immediately.

  2. Document how many fields you still need to create.

  3. Contact Dazos Support with the following information:

    • Exact error message received

    • Affected module (Leads, Accounts, Contacts, etc.)

    • Number of additional fields needed

    • Your instance URL

    • Screenshots of the error

πŸ’‘ Tip: While waiting for resolution, consider using existing fields for a similar purpose, utilizing module table fields for repeating data, or removing unused custom fields to free up capacity.

βœ… Best Practice: Reuse fields across layouts instead of duplicating them, and plan your field structure before implementation to avoid hitting limits.

Escalation

Contact Dazos Support immediately. This issue requires:

  • Database schema analysis by Tier 3 developers

  • Backend field audit and cleanup

  • Potential database table modifications

πŸ“§ Support Contact: [email protected]

Did this answer your question?