Troubleshooting

This guide covers common issues with lead naming rules and pipeline creation settings.

Naming Rule Issues

Lead name not generating automatically

Symptoms:

• Lead name stays empty or shows manual text

• Naming rule appears active but has no effect

Causes:

1. No naming rule is currently active

2. The required fields in the pattern are empty on the lead

3. The lead name was manually entered before the rule could apply

Solutions:

1. Verify a naming rule is active: CRM ‣ Configuration ‣ Lead Naming Rules. Check that exactly one rule has the Active checkbox enabled.

2. Ensure the lead has data in the fields used by the pattern. For example, if the pattern is {company} - {contact}, both the company and contact fields must have values.

3. Clear the lead name field manually and then re-enter or re-save the lead to trigger the naming rule.

Generated name looks wrong

Symptoms:

• Name has extra separators (e.g., “Acme Corp - - Website”)

• Name is missing expected parts

• Name shows field codes literally (e.g., “{company}”)

Causes:

1. Empty fields creating separator artifacts

2. Fields referenced in the pattern don’t exist or have different names

3. Pattern syntax error

Solutions:

1. The system should automatically skip empty fields and collapse separators. If this isn’t working, check the rule’s separator configuration.

2. Verify that the field codes in your pattern match the available codes. Open the naming rule and review the field code reference.

3. Edit the naming rule and check for typos in the pattern. Field codes must use the exact syntax shown in the field code reference.

Bulk apply wizard not working

Symptoms:

• Wizard button does not appear

• Wizard runs but no leads are renamed

• Wizard shows zero affected leads

Causes:

1. User does not have Sales / Administrator permissions

2. All leads already match the naming pattern

3. No leads exist in the selected scope

Solutions:

1. Verify your user has the Sales / Administrator group. Contact your system administrator if needed.

2. The wizard only renames leads whose current name differs from what the pattern would generate. If all leads already match, the count shows zero.

3. Check the wizard’s filter/scope settings. Ensure you are targeting the correct set of leads.

Multiple naming rules conflict

Symptoms:

• Unexpected naming behavior after creating a new rule

• Old rule still seems to apply

Causes:

Only one naming rule can be active at a time. If you activate a new rule, the previous one should automatically deactivate.

Solutions:

1. Navigate to CRM ‣ Configuration ‣ Lead Naming Rules

2. Verify only one rule has the Active checkbox enabled

3. If multiple rules appear active, deactivate all and then activate only the desired one

Pipeline Settings Issues

Quick-create dialog unchanged after settings update

Symptoms:

• Changed pipeline settings but quick-create still shows old fields

• New default values not applying

Causes:

1. Browser cache showing the old form

2. Settings saved for a different sales team

3. Settings not saved

Solutions:

1. Hard-refresh the browser (Ctrl+Shift+R or Cmd+Shift+R) to clear the cached form views.

2. Verify the settings are for the correct sales team. Each team can have its own pipeline creation settings.

3. Ensure you clicked Save after making changes.

New leads not getting default values

Symptoms:

• Leads created from pipeline don’t have the expected default salesperson, tags, or other values

Causes:

1. Defaults are configured for a different team

2. The user creating the lead is not a member of the configured team

3. Manual values override defaults

Solutions:

1. Check the pipeline creation settings for the specific team visible in the pipeline view.

2. Ensure the creating user is assigned to the correct sales team.

3. Default values only fill empty fields. If a user manually enters a value in the quick-create dialog, it overrides the default.

Getting Help

If your issue isn’t covered here:

1. Check the naming rule configuration in CRM ‣ Configuration ‣ Lead Naming Rules

2. Enable Developer Mode (Settings ‣ Activate Developer Mode) for detailed error messages

3. Contact your system administrator with:

   • The naming rule pattern being used

   • A specific lead example showing the issue

   • Expected vs actual name output

   • Screenshots of the rule configuration