Bug: Renaming custom fields creates new fields

  • Resolved jlhiggs

    (@jlhiggs)


    2 years, 7 months ago

    Hi, when a custom field is renamed in Jetpack CRM, it seems to actually create a new field. The outcome is that any data already entered in the field is effectively lost (it’s still present in the WP database, but inaccessible as far as users are concerned).

    This occurs for both Contact custom fields and Company custom fields.

    Repro:
    1. In WP admin, go to Jetpack CRM > Settings > Custom Fields
    2. Create a Contact Custom Field, naming it “Test Field 1”, and click the Save Custom Fields button
    3. Open up any Contact record for editing, enter something in Test Field 1, and save the record
    4. Go back to Settings > Custom Fields, change the name of the custom field from “Test Field 1” to “Test Field 2”, and click the Save Custom Fields button
    5. Go back to the Contact record that you previously edited: You’ll find that Test Field 2 is now displayed, and there is no data in it.

    This will be a real pain for users who’ve already populated a lot of Contact and/or Company records, as they’ll have to figure out what was in the old field and update all their records again. It’s an odd user experience that renaming an existing field should create a new field at all, but if it has to work that way, then existing data should be automatically migrated to the new field.

Viewing 3 replies - 1 through 3 (of 3 total)
  • Jay

    (@bluejay77)

    Hi @jlhiggs,

    Thank you for your report and including the detailed instructions to reproduce the issue. In short, this is a known issue and I’ve added your report to our internal issue tracker.

    I’ll add a bit of detail below in case other users run into the same issue and looking for a workaround.

    The issue here is that “renaming” the custom field also regenerates the slug. The fact that it changes the slug stops the data from being brought through that was linked to the custom field.

    The outcome is that any data already entered in the field is effectively lost (it’s still present in the WP database, but inaccessible as far as users are concerned).

    As you say, the data is actually present in the database. If a user wants to bring the data back, they can rename it back to what it was.

    I hope that helps! We’ll keep an eye on this issue and let you know when we have a fix for this issue.

    Thread Starter jlhiggs

    (@jlhiggs)

    Ok great, thank you. Good to hear that it’s a known issue, and looking forward to hearing when the fix is available!

    Plugin Support Stef (a11n)

    (@erania-pinnera)

    Hey @jlhiggs,

    You’re welcome ??

    I’m going to mark this thread as solved. If you have any further questions or need some more help, you’re welcome to open another thread here. Cheers!

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Bug: Renaming custom fields creates new fields’ is closed to new replies.