Ability to change field type for collection fields

I often have that as a website and its content grows I need to change what used to be a plain text field into a rich text field. Or a numbers field into a plain text one.

Now the only way to do this is very labor-intensive... create the new rich text field, copy-paste all the old content from the plain text field into the new rich text field and then go into the pages that have that collection in it and connect it to the new rich text field.

A simple option in the Collection to alter the field type would be such a time saver.

  • Marcel Deelen
  • Jan 13 2020
  • Reviewed
CMS
  • Growth Data Product commented
    18 Dec 10:37

    This would be a great

  • Tim deSilva commented
    20 Sep 19:31

    100% needed

  • David Tischler commented
    11 Jul 23:02

    This is an insanely bothersome thing to have to deal with. Also wish this had a quick solution.

  • Jacob Schlegel commented
    September 30, 2023 12:13

    YES! Little things like this would be so helpful.

  • Joachim Wernersson commented
    September 07, 2023 09:14

    Yeah this would be a great feature

  • Jon Q commented
    July 22, 2023 18:21

    I just ran into a need for this. Being able to convert a plain-text field type to rich field would be very helpful :)

  • Brian Dawson commented
    May 18, 2022 13:24

    I really didn't want to copy/paste data from my old field to a new field, so I used Parabola as a workaround.

    Essentially, here are the steps:

    1. Create new field in collection.

    2. Create Parabola flow

    3. In Parabola flow:

      1. Pull in collection and all its fields

      2. Add a "Send to Webflow" step

      3. Set up that step to overwrite the new field (which would be blank) with the old field's data.

    Possible in about 5-15 minutes if you're familiar with Parabola.

    I wrote up my use case as an example, here.

    Hope that helps someone.

    But still, allowing field changes within a collection would make things much simpler!

  • Jennifer BeVard commented
    March 30, 2022 22:16

    I've come up against this with Text Fields. Requirements change and it would be nice to convert it to a Rich Text Field.

  • Vinícius Sgarbe commented
    March 09, 2022 19:48

    I BEG YOU

  • Bryan Perdue commented
    July 26, 2021 19:57

    Please do this

  • SGFCreatives commented
    July 17, 2021 21:49

    Literally dying for this.

  • Bruno commented
    June 28, 2021 00:41

    Yes, this feature is much needed. Please bump.

  • Shafic Rawdah commented
    May 24, 2021 19:28

    bump

  • Michael Payne commented
    May 17, 2021 10:57

    Yes, this would be a really useful addition

  • Joel Downs commented
    April 16, 2021 21:45

    Need.

  • Zack Steven commented
    March 10, 2021 18:01

    This is much needed. In my case, members are linking to their personal websites but inevitably don't insert a valid URL. When Memberstack goes to update their corresponding CMS item, Zapier returns an invalid URL error message. We should either be able to change the type of a CMS field or URL validation in forms should be an option alongside email, phone, etc.

  • Thinklittle commented
    February 18, 2021 00:08

    need

  • Colin Chaloner commented
    January 24, 2021 15:09

    Argh. Yes, this is definitely needed. Torn between re-importing & relinking everything to fix, or replacing all plain text elements with rich text. Neither ideal. Ability to change after the fact would make a huge difference.

  • Alexandra Sloves commented
    November 26, 2020 13:33

    NEED :)

  • Sonia Morales commented
    August 13, 2020 18:14

    Need This!!!

  • Load older comments
  • +54