# Add ability to fully edit fields after creation

**URL:** <https://community.fibery.io/t/add-ability-to-fully-edit-fields-after-creation/1077>\
**Category:** Ideas & Features\
**Tags:** flexible-domain\
**Created:** [October 16, 2020, 1:53am UTC](https://community.fibery.io/t/add-ability-to-fully-edit-fields-after-creation/1077 "2020-10-16T01:53:30Z")\
**Posts on this page:** 19\
**Page:** 1

<div class="post-metadata">

**Author:** ![Oshyan](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/oshyan/32/11431_2.png) [@Oshyan](https://community.fibery.io/u/Oshyan)\
**Post date:** [October 16, 2020, 1:53am UTC](https://community.fibery.io/t/add-ability-to-fully-edit-fields-after-creation/1077/1 "2020-10-16T01:53:30Z")

</div>

One thing I’m finding increasingly frustrating is the inability to edit most aspects of Fields after they’re created. Notion seems to be able to handle this much better, even allowing you to convert between field types (e.g. text vs. multi-select) and maintain some of the data.

Another common challenge I run into with this is not being able to set the Default Value after creating the Field. Sometimes I realize later that I want a default value, or sometimes I decide to change it after using it with another value for some time.

This kind of rigidity in certain areas definitely puts a damper on the overall flexible concept and promise of Fibery. I want to feel like I can adjust and modify my setup based on changing workflow or increased understanding of the system over time. But in some ways I really can’t ([Move Entity to another Type](https://community.fibery.io/t/move-entity-to-another-type/528) is another example of where this comes up).

---

<div class="post-metadata">

**Author:** ![B\_Sp](https://avatars.discourse-cdn.com/v4/letter/b/e8c25b/32.png) [@B\_Sp](https://community.fibery.io/u/B_Sp)\
**Post date:** [October 16, 2020, 2:22am UTC](https://community.fibery.io/t/add-ability-to-fully-edit-fields-after-creation/1077/2 "2020-10-16T02:22:06Z")

</div>

100% agree, couldn’t have said it any better. This is an issue I deal with as well too, many times daily as my Fibery Instance expands.

Re: Default values, I think it’s another feature that is unfinished. It is actually something Notion DOES NOT have, although they solve it in Templates which we chatted about recently. But I don’t understand why the Fibery team passed up doing it in multi-select fields:

> [@Add Default Value on Multi-Select Fields](https://community.fibery.io/t/add-default-value-on-multi-select-fields/891):
>
> Hi guys, The default value option on Single-Select fields… is a very nice feature. It allows you to determine if you would like a tag to get picked up by each new entry, or not. This is another feature absent in Notion! I could really use it in the Multi-select field. I was hoping that since Multi-Select is new (released in April per below) perhaps you simply haven’t gotten to its implementation? I use this default value extensively in single-selec…

But you are right it is a real pain not being able to edit fields/relations after you create them.

---

<div class="post-metadata">

**Author:** ![Pawel\_Badenski](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/pawel_badenski/32/1980_2.png) [@Pawel\_Badenski](https://community.fibery.io/u/Pawel_Badenski)\
**Post date:** [July 28, 2021, 2:14pm UTC](https://community.fibery.io/t/add-ability-to-fully-edit-fields-after-creation/1077/3 "2021-07-28T14:14:54Z")

</div>

Is there any workaround for this perhaps? It creates a rather harsh feedback loop “unless you get this right the first time…”

---

<div class="post-metadata">

**Author:** ![Pawel\_Badenski](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/pawel_badenski/32/1980_2.png) [@Pawel\_Badenski](https://community.fibery.io/u/Pawel_Badenski)\
**Post date:** [July 29, 2021, 4:31pm UTC](https://community.fibery.io/t/add-ability-to-fully-edit-fields-after-creation/1077/4 "2021-07-29T16:31:22Z")

</div>

FYI I found a workaround for this for some fields. I renamed my “field” to “field\_old”. Then create a new “field” with correct schema. I then open Entity in Table View, select whole “field\_old” column and copy/paste to “field” column.

It doesn’t work for “Rich text” - so be careful when deciding to use “Rich text” for your fields 😉

---

<div class="post-metadata">

**Author:** ![mdubakov](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/mdubakov/32/10_2.png) [@mdubakov](https://community.fibery.io/u/mdubakov)\
**Post date:** [January 6, 2022, 9:50am UTC](https://community.fibery.io/t/add-ability-to-fully-edit-fields-after-creation/1077/5 "2022-01-06T09:50:34Z")

</div>

Implementation started for basic fields (text, number, date)

---

<div class="post-metadata">

**Author:** ![Nick\_Frolov](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/nick_frolov/32/4918_2.png) [@Nick\_Frolov](https://community.fibery.io/u/Nick_Frolov)\
**Post date:** [April 6, 2022, 1:00pm UTC](https://community.fibery.io/t/add-ability-to-fully-edit-fields-after-creation/1077/6 "2022-04-06T13:00:35Z")

</div>

this workaround works, but if you have dozens of different views and charts created (which use filter on the field which you want to change), then this trick won’t work

---

<div class="post-metadata">

**Author:** ![Simeon\_Payne](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/simeon_payne/32/5928_2.png) [@Simeon\_Payne](https://community.fibery.io/u/Simeon_Payne)\
**Post date:** [December 9, 2022, 2:35pm UTC](https://community.fibery.io/t/add-ability-to-fully-edit-fields-after-creation/1077/7 "2022-12-09T14:35:52Z")

</div>

Very new to Fibery, how do you select a whole field, can’t find an option to do this to allow copy and paste.

---

<div class="post-metadata">

**Author:** ![Chr1sG](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/chr1sg/32/3941_2.png) [@Chr1sG](https://community.fibery.io/u/Chr1sG)\
**Post date:** [December 9, 2022, 2:58pm UTC](https://community.fibery.io/t/add-ability-to-fully-edit-fields-after-creation/1077/8 "2022-12-09T14:58:13Z")

</div>

> [@Simeon\_Payne](#):
>
> how do you select a whole field

Not sure what you mean by the ‘whole field’.  
Do you mean ‘select the value of a field and copy-paste into another field for all entities at once’?

---

<div class="post-metadata">

**Author:** ![ESGdataBoi](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/esgdataboi/32/11960_2.png) [@ESGdataBoi](https://community.fibery.io/u/ESGdataBoi)\
**Post date:** [December 9, 2022, 3:29pm UTC](https://community.fibery.io/t/add-ability-to-fully-edit-fields-after-creation/1077/9 "2022-12-09T15:29:57Z")

</div>

I could be wrong, but I think he means something similar to excel or google sheets where you select the associated field name in the column header and it selects all “cells” within that column. I would naturally like that too, however I know it’s because I developed a false expectation from using spreadsheets my whole career (whereas this shouldn’t be a priority in a database-style system in all reality).

---

<div class="post-metadata">

**Author:** ![Simeon\_Payne](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/simeon_payne/32/5928_2.png) [@Simeon\_Payne](https://community.fibery.io/u/Simeon_Payne)\
**Post date:** [December 9, 2022, 3:42pm UTC](https://community.fibery.io/t/add-ability-to-fully-edit-fields-after-creation/1077/10 "2022-12-09T15:42:19Z")

</div>

Please see the workaround for changing field settings in the post above mine.

I have raised the new field but cannot see how to copy the old one over to it.

regards

Simeon

---

<div class="post-metadata">

**Author:** ![Chr1sG](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/chr1sg/32/3941_2.png) [@Chr1sG](https://community.fibery.io/u/Chr1sG)\
**Post date:** [December 9, 2022, 4:17pm UTC](https://community.fibery.io/t/add-ability-to-fully-edit-fields-after-creation/1077/11 "2022-12-09T16:17:06Z")

</div>

To copy-pasteall values from one field to another, you will need to create a table view (if you don’t already have one) so you can see all entities, with the source and destination columns visible.  
Then you need to select all the cells in the source column (and the only way is to manually highlight them using the mouse or shift+cursor keys), press Ctrl-C, then select the top cell in the destination column and press Ctrl-V.

(Ctrl → Cmd on Mac 🙂)

---

<div class="post-metadata">

**Author:** ![jondkinney](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/jondkinney/32/6061_2.png) [@jondkinney](https://community.fibery.io/u/jondkinney)\
**Post date:** [July 7, 2023, 12:21pm UTC](https://community.fibery.io/t/add-ability-to-fully-edit-fields-after-creation/1077/12 "2023-07-07T12:21:02Z")

</div>

Any update on the ability to change the type of a field? Notion allows this easily after creation, but seems much more rigid here. My current use case is changing a date time to a simple date. I understand in this instance (and possibly most change instances) there will be data loss, but perhaps you could pop up a dialog describing that and let the power users more effectively manage their space?

---

<div class="post-metadata">

**Author:** ![drew](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/drew/32/10581_2.png) [@drew](https://community.fibery.io/u/drew)\
**Post date:** [February 21, 2025, 8:13pm UTC](https://community.fibery.io/t/add-ability-to-fully-edit-fields-after-creation/1077/13 "2025-02-21T20:13:03Z")

</div>

Voting for this as I often need to convert fields from formulas to editable and vice versa, which today requires brand new fields that must be completely re-referenced everywhere. Like others, I greatly miss Notion & Coda’s ability to convert easily later, maintaining all relations/connections. And then there’s **Integer** vs **Floating**. I’ve been unable to display certain numbers without decimals since apparently even the formatting depends on low level field type(?). Finally, I wish I could quickly _duplicate_ & modify, though admittedly that’s a separate feature request.

---

<div class="post-metadata">

**Author:** ![tomp](https://avatars.discourse-cdn.com/v4/letter/t/3da27b/32.png) [@tomp](https://community.fibery.io/u/tomp)\
**Post date:** [April 4, 2025, 8:29am UTC](https://community.fibery.io/t/add-ability-to-fully-edit-fields-after-creation/1077/14 "2025-04-04T08:29:23Z")

</div>

The team do great work but i find it a little frustrating to see development of new features when the basics are still not right in many ways, I would like to be able to convert single select to multi select field.

---

<div class="post-metadata">

**Author:** ![tycecycle](https://avatars.discourse-cdn.com/v4/letter/t/848f3c/32.png) [@tycecycle](https://community.fibery.io/u/tycecycle)\
**Post date:** [May 27, 2025, 4:25pm UTC](https://community.fibery.io/t/add-ability-to-fully-edit-fields-after-creation/1077/15 "2025-05-27T16:25:30Z")

</div>

Really hope this gets prioritized. I just ran into the same issue as [Add ability to fully edit fields after creation - #12 by jondkinney](https://community.fibery.io/t/add-ability-to-fully-edit-fields-after-creation/1077/12). I selected “include time” on a date field to see what a week calendar view would look like, and now when I want to switch back to not including a time, I can’t.

---

<div class="post-metadata">

**Author:** ![RonMakesSystems](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/ronmakessystems/32/14122_2.png) [@RonMakesSystems](https://community.fibery.io/u/RonMakesSystems)\
**Post date:** [November 5, 2025, 8:22pm UTC](https://community.fibery.io/t/add-ability-to-fully-edit-fields-after-creation/1077/16 "2025-11-05T20:22:04Z")

</div>

Adding another one to the list:  
Editing lookup after creation, as long as the final output type is the same.

---

<div class="post-metadata">

**Author:** ![B\_Sp](https://avatars.discourse-cdn.com/v4/letter/b/e8c25b/32.png) [@B\_Sp](https://community.fibery.io/u/B_Sp)\
**Post date:** [March 24, 2026, 11:53pm UTC](https://community.fibery.io/t/add-ability-to-fully-edit-fields-after-creation/1077/17 "2026-03-24T23:53:12Z")

</div>

Wanted to add a bump here although I don’t have a vote to spare! I have been doing a lot of tweaking in our Fibery instance and running across this frequently during this stretch - had actually lost track of whether it was a feature request, and also was thinking about Notion after paying for a month of “Business” in there to look around at a lot of what they are doing, in particular with the AI, and to @Oshyan’s point here from 5 1/2 years ago granted, this is has been an annoyance given my instance is a bit older than that and we have a lot of stuff in here.

> [@Oshyan](#):
>
> Notion seems to be able to handle this much better, even allowing you to convert between field types (e.g. text vs. multi-select) and maintain some of the data.

Most recently I wanted to simply change a single-select to multi-select in one of our original db’s because it turns out the content in there and how we treat it has evolved. Only way to get that done is a mass copy/paste exercise and I don’t want to lose the history in the old field once it’s deleted…agree with @tycecycle that this really should be prioritized soon!

---

<div class="post-metadata">

**Author:** ![mdubakov](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/mdubakov/32/10_2.png) [@mdubakov](https://community.fibery.io/u/mdubakov)\
**Post date:** [June 25, 2026, 12:58pm UTC](https://community.fibery.io/t/add-ability-to-fully-edit-fields-after-creation/1077/18 "2026-06-25T12:58:54Z")

</div>

Now you can set default values for basic fields

> [@June 25, 2026 / brick Custom Apps, AI credits & extra usage, Better performance for large tables, Set static default values for basic fields, Automations history](https://community.fibery.io/t/june-25-2026-custom-apps-ai-credits-extra-usage-better-performance-for-large-tables-set-static-default-values-for-basic-fields-automations-history/11012?sort=top):
>
> Yesterday we had a [very long degraded performance incident](https://status.fibery.io/cmqrvsgt200dt2io3o9dg756z) for integrations, reports and automations. We still didn’t identify the root cause (and even AI feels helpless here). The incident has nothing to do with today’s release, but if things will go south again, blame the heatwave hot_face and MongoDB. Custom Apps (experimental) Fibery now lets you build your own Apps — custom, client-side UI that runs on top of your workspace data. Now any user can build custom solutions tailored for speci…

---

<div class="post-metadata">

**Author:** ![mdubakov](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/mdubakov/32/10_2.png) [@mdubakov](https://community.fibery.io/u/mdubakov)\
**Post date:** [August 6, 2026, 2:19pm UTC](https://community.fibery.io/t/add-ability-to-fully-edit-fields-after-creation/1077/19 "2026-08-06T14:19:12Z")

</div>

> [@tomp](#):
>
> I would like to be able to convert single select to multi select field.

now you can convert single-select field to multi-select [August 6, 2026 / Custom Apps improvements, Convert Select field to Database, Update small part of rich text and add comments via MCP](https://community.fibery.io/t/august-6-2026-custom-apps-improvements-convert-select-field-to-database-update-small-part-of-rich-text-and-add-comments-via-mcp/11145)
