Option to set a Default Value for specific fields in Collections

Would be great if there was an option when creating a CMS Collection to set a Default Value for things like "Plain Text" and other fields. This would work great for embed codes using CMS and things like that for recommending certain Values for clients. 

For example: If I was embedding a Music Store Player using an iFrame. I already have fields where the client just has to enter their player iD number for their specific store. Then a couple other fields to select width and height if they want and although specific heights and widths are recommended in the "Help Text" fields, I think taking it a step further and being able to enter a default value would be great. That way they wouldn't have to change it but they can if they really wanted to.

  • Noah Raskin
  • Dec 27 2017
CMS
  • Steve Graham commented
    25 Nov 08:59pm

    I'm extremely surprised this is not a feature already; especially for switches.

  • Lucian Chevallier commented
    26 Apr 03:25pm

    This would be great! Especially for toggles

  • Jon Stastny commented
    29 Nov, 2023 05:47pm

    How is this not a thing yet??

  • Hürkan Gökkaya commented
    30 Aug, 2023 08:43am

    Need it

  • Jeffrey Barron commented
    15 Aug, 2023 01:49am

    Essential really, Basic UX


  • Basti Haus commented
    4 Aug, 2023 12:46pm

    Need thisss

  • Miles Mitchell commented
    4 May, 2023 08:50pm

    Gahhh this would be awesome and so helpful for clients to keep your designs working as intended.

  • BC Technologies commented
    1 Dec, 2022 10:15am

    5 years since first requested - basic functionality still not implemented.

  • Tuomas Pitkänen commented
    27 May, 2022 07:45am

    This would be great!

  • Julie Lim commented
    21 Sep, 2021 07:36pm

    Hopefully they're working on this because this would be suuuuper helpful

  • Josh commented
    21 Apr, 2021 01:03pm

    Would love to see this implemented!

  • Szymon Zurek commented
    1 Mar, 2021 05:50am

    This would be great! I really need this for Zapier integrations too. This way I would be able to label different forms accordingly, as some Zaps don't allow to just use the form ID as the label.

  • Julien V. commented
    8 Feb, 2021 11:22am

    Useful for CMS collections populated with Zapier with multi-reference fields

  • Verve Light commented
    10 Oct, 2020 07:03am

    This would be super useful, especially when adding a new field to an already established CMS table.

  • +47