# \#flexible-domain

**URL:** https://community.fibery.io/tag/flexible-domain/3.md

[Latest](https://community.fibery.io/latest.md) · [Categories](https://community.fibery.io/categories.md) · [Tags](https://community.fibery.io/tags.md)

---

## [Add Duration as a valid field type](https://community.fibery.io/t/add-duration-as-a-valid-field-type/3710)

<div class="topic-metadata">

**Author:** [@julien.erny](https://community.fibery.io/u/julien.erny)\
**Replies:** 4\
**Last updated:** [October 1, 2026, 4:25pm UTC](https://community.fibery.io/t/add-duration-as-a-valid-field-type/3710 "2026-10-01T16:25:12Z")

</div>

Today, Duration is not a valid field type so you necessarily have to convert a duration in days, hours or minutes. It would be great to have the Duration be a full class citizen in fields with a textual representation dy…

---

## [\[DONE\] Show Field References](https://community.fibery.io/t/done-show-field-references/6093)

<div class="topic-metadata">

**Author:** [@njyo](https://community.fibery.io/u/njyo)\
**Replies:** 1\
**Last updated:** [September 24, 2026, 1:59pm UTC](https://community.fibery.io/t/done-show-field-references/6093 "2026-09-24T13:59:26Z")

</div>

Whenever I need to refactor my databases because I want to move some fields from one entity to another I always have to enact my changes and then see what these changes broke and then fix them. Especially for formulae a…

---

## [\[APPROVED\] Polymorphic relations. When creating relation, ability to have many Types from which to choose, and not just one Type](https://community.fibery.io/t/approved-polymorphic-relations-when-creating-relation-ability-to-have-many-types-from-which-to-choose-and-not-just-one-type/425)

<div class="topic-metadata">

**Author:** [@B\_Sp](https://community.fibery.io/u/B_Sp)\
**Replies:** 75\
**Last updated:** [September 15, 2026, 4:35am UTC](https://community.fibery.io/t/approved-polymorphic-relations-when-creating-relation-ability-to-have-many-types-from-which-to-choose-and-not-just-one-type/425 "2026-09-15T04:35:34Z")

</div>

Hi again, As I get into Fibery, I am seeing that it could be useful for my use case to be able to choose amongst all types in a given App when creating a related field in another type. What I mean here is let’s say I h…

---

## [\[APPROVED\] New Field Type: JSON](https://community.fibery.io/t/approved-new-field-type-json/9816)

<div class="topic-metadata">

**Author:** [@DominikM](https://community.fibery.io/u/DominikM)\
**Replies:** 16\
**Last updated:** [September 11, 2026, 8:37am UTC](https://community.fibery.io/t/approved-new-field-type-json/9816 "2026-09-11T08:37:01Z")

</div>

would like to pass the “speakers” from fireflies (like e-mails) as json (array) to fibery and then run some automations (with rules), as example: to identify the fibery users which are existing for this e-mails and link …

---

## [Colour Field Type](https://community.fibery.io/t/colour-field-type/3137)

<div class="topic-metadata">

**Author:** [@cannibalflea](https://community.fibery.io/u/cannibalflea)\
**Replies:** 2\
**Last updated:** [September 10, 2026, 2:23pm UTC](https://community.fibery.io/t/colour-field-type/3137 "2026-09-10T14:23:46Z")

</div>

This might be a bit out there, but I was wondering if it makes sense to include a “Colour/Color” field type. I think if there is a possibility of colouring cards in the future, it might be good to be able to predefine th…

---

## [\[DONE\] Convert select fields into regular databases](https://community.fibery.io/t/done-convert-select-fields-into-regular-databases/6629)

<div class="topic-metadata">

**Author:** [@helloitse](https://community.fibery.io/u/helloitse)\
**Replies:** 24\
**Last updated:** [August 6, 2026, 2:23pm UTC](https://community.fibery.io/t/done-convert-select-fields-into-regular-databases/6629 "2026-08-06T14:23:21Z")

</div>

Is it possible to allow us to import from a single/multi select? When setting up a new type to replace a select field (I had originally setup a select field but ran into limitations when grouping and nesting entities) it…

---

## [\[DONE\] Convert select options to database](https://community.fibery.io/t/done-convert-select-options-to-database/10035)

<div class="topic-metadata">

**Author:** [@AdVhPkgKad](https://community.fibery.io/u/AdVhPkgKad)\
**Replies:** 3\
**Last updated:** [August 6, 2026, 2:21pm UTC](https://community.fibery.io/t/done-convert-select-options-to-database/10035 "2026-08-06T14:21:52Z")

</div>

I have a select that I want to duplicate to multiple database locations (perhaps even using the values to link two entities automatically). As since this release, it has been possible to copy the select from one databas…

---

## [Add ability to fully edit fields after creation](https://community.fibery.io/t/add-ability-to-fully-edit-fields-after-creation/1077)

<div class="topic-metadata">

**Author:** [@Oshyan](https://community.fibery.io/u/Oshyan)\
**Replies:** 18\
**Last updated:** [August 6, 2026, 2:19pm UTC](https://community.fibery.io/t/add-ability-to-fully-edit-fields-after-creation/1077 "2026-08-06T14:19:12Z")

</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 (…

---

## [Allow using a Formula to define Default Values](https://community.fibery.io/t/allow-using-a-formula-to-define-default-values/1929)

<div class="topic-metadata">

**Author:** [@Matt\_Blais](https://community.fibery.io/u/Matt_Blais)\
**Replies:** 4\
**Last updated:** [July 28, 2026, 12:16pm UTC](https://community.fibery.io/t/allow-using-a-formula-to-define-default-values/1929 "2026-07-28T12:16:57Z")

</div>

I suppose this is identical in function to using an Action to define a field value when an entity is created, if a Formula is used. But “default value” is a simpler idea than “Action, triggered upon entity creation, etc”…

---

## [Make “Last Modified By” Available as a Database Field](https://community.fibery.io/t/make-last-modified-by-available-as-a-database-field/8477)

<div class="topic-metadata">

**Author:** [@Edan](https://community.fibery.io/u/Edan)\
**Replies:** 6\
**Last updated:** [June 28, 2026, 1:14pm UTC](https://community.fibery.io/t/make-last-modified-by-available-as-a-database-field/8477 "2026-06-28T13:14:23Z")

</div>

I can’t find a way to display who modified an entity—only the last modified date. @mdubakov mentioned in this thread that it was implemented, but I can’t find it anywhere: It’d be great to access even more existing f…

---

## [\[DONE\] Add Default Value for Checkbox Type](https://community.fibery.io/t/done-add-default-value-for-checkbox-type/2035)

<div class="topic-metadata">

**Author:** [@Matt\_Blais](https://community.fibery.io/u/Matt_Blais)\
**Replies:** 4\
**Last updated:** [June 25, 2026, 1:00pm UTC](https://community.fibery.io/t/done-add-default-value-for-checkbox-type/2035 "2026-06-25T13:00:25Z")

</div>

Apparently Checkbox fields are always given a Default Value of False. It would be useful to be able to specify True/False in the Type definition. I know I can write a Rule for “Entity Created” to set the default value. …

---

## [Allow changing the field type from DateTime → Date](https://community.fibery.io/t/allow-changing-the-field-type-from-datetime-date/10642)

<div class="topic-metadata">

**Author:** [@ID.000](https://community.fibery.io/u/ID.000)\
**Replies:** 6\
**Last updated:** [June 1, 2026, 4:47pm UTC](https://community.fibery.io/t/allow-changing-the-field-type-from-datetime-date/10642 "2026-06-01T16:47:20Z")

</div>

We ran into a limitation while working with Date fields that include time. Our team works across multiple time zones, and we noticed that storing date + time sometimes creates inconsistencies in how entities appear for …

---

## [Ability to create "non-defined" or "orphan" Entity for later inclusion after analysis - and queue of such entities](https://community.fibery.io/t/ability-to-create-non-defined-or-orphan-entity-for-later-inclusion-after-analysis-and-queue-of-such-entities/10794)

<div class="topic-metadata">

**Author:** [@B\_Sp](https://community.fibery.io/u/B_Sp)\
**Replies:** 0\
**Last updated:** [May 1, 2026, 9:28pm UTC](https://community.fibery.io/t/ability-to-create-non-defined-or-orphan-entity-for-later-inclusion-after-analysis-and-queue-of-such-entities/10794 "2026-05-01T21:28:30Z")

</div>

This feels like something that has been discussed multiple times since I joined this forum in 2019, but right now I’m not sure if this is a feature request, or has otherwise been addressed, but it seems like a valid need…

---

## [Auto-linking via a to-many relation \[workaround\]](https://community.fibery.io/t/auto-linking-via-a-to-many-relation-workaround/2701)

<div class="topic-metadata">

**Author:** [@Polina\_Zenevich](https://community.fibery.io/u/Polina_Zenevich)\
**Replies:** 8\
**Last updated:** [April 16, 2026, 1:08pm UTC](https://community.fibery.io/t/auto-linking-via-a-to-many-relation-workaround/2701 "2026-04-16T13:08:45Z")

</div>

Hi, folks! Hope, this workaround would be helpful for someone. If you have any questions or suggestions - feel free, to share them here, in comments :hugs: Problem There are two Databases you would like to connect via …

---

## [Stable technical identifier (system name / alias) for fields](https://community.fibery.io/t/stable-technical-identifier-system-name-alias-for-fields/10635)

<div class="topic-metadata">

**Author:** [@ID.000](https://community.fibery.io/u/ID.000)\
**Replies:** 4\
**Last updated:** [March 25, 2026, 9:49am UTC](https://community.fibery.io/t/stable-technical-identifier-system-name-alias-for-fields/10635 "2026-03-25T09:49:33Z")

</div>

Hi Fibery team :slightly\_smiling\_face: It would be extremely helpful if fields had a stable technical identifier (system name / alias) that formulas, automations, and integrations could reference. Currently, field refe…

---

## [Relationship properties](https://community.fibery.io/t/relationship-properties/887)

<div class="topic-metadata">

**Author:** [@Chr1sG](https://community.fibery.io/u/Chr1sG)\
**Replies:** 42\
**Last updated:** [March 10, 2026, 1:24am UTC](https://community.fibery.io/t/relationship-properties/887 "2026-03-10T01:24:02Z")

</div>

This might be a big ask, but would it be possible to add properties to relationships as well as entities (like is possible with a graph database)? I realise that the more sophisticated you make the underlying platform, …

---

## [Time only fields](https://community.fibery.io/t/time-only-fields/8851)

<div class="topic-metadata">

**Author:** [@danielbmarsh](https://community.fibery.io/u/danielbmarsh)\
**Replies:** 6\
**Last updated:** [February 12, 2026, 3:25pm UTC](https://community.fibery.io/t/time-only-fields/8851 "2026-02-12T15:25:20Z")

</div>

I have run into many use cases where I don’t need the date associated with a time field. Why because the entity itself is already associated with a day, or the is no day associated with the time. I will give some exampl…

---

## [Relation select dialog needs to show ids](https://community.fibery.io/t/relation-select-dialog-needs-to-show-ids/10221)

<div class="topic-metadata">

**Author:** [@Yuri\_BC](https://community.fibery.io/u/Yuri_BC)\
**Replies:** 0\
**Last updated:** [January 5, 2026, 11:15am UTC](https://community.fibery.io/t/relation-select-dialog-needs-to-show-ids/10221 "2026-01-05T11:15:35Z")

</div>

This is frequently occurring need and tension: When selecting a related entity in the dropdown search select dialog of a to-one relation (e.g. pinned field) the suggested items only show Name field, not Public I’d. This…

---

## [Hierarchical Relation Fields](https://community.fibery.io/t/hierarchical-relation-fields/2147)

<div class="topic-metadata">

**Author:** [@cannibalflea](https://community.fibery.io/u/cannibalflea)\
**Replies:** 1\
**Last updated:** [November 8, 2023, 10:54pm UTC](https://community.fibery.io/t/hierarchical-relation-fields/2147 "2023-11-08T22:54:31Z")

</div>

Fibery supports creating hierarchies of entities where entities of the same type (e.g. meeting types) can be nested inside others, thus creating a hierarchical list or tree type structure. This can be visualized quite we…

---

## [Archive Databases/Spaces without Deletion](https://community.fibery.io/t/archive-databases-spaces-without-deletion/8208)

<div class="topic-metadata">

**Author:** [@helloitse](https://community.fibery.io/u/helloitse)\
**Replies:** 3\
**Last updated:** [December 3, 2025, 10:35am UTC](https://community.fibery.io/t/archive-databases-spaces-without-deletion/8208 "2025-12-03T10:35:26Z")

</div>

As companies grow and evolve some databases should become read-only and/or removed from day to day operations. How are people handling this right now? I often avoid creating databases in Fibery for small projects or pro…

---

## [Regex to verify a field entry](https://community.fibery.io/t/regex-to-verify-a-field-entry/2105)

<div class="topic-metadata">

**Author:** [@Claude\_de\_Loupy](https://community.fibery.io/u/Claude_de_Loupy)\
**Replies:** 10\
**Last updated:** [November 19, 2025, 10:45pm UTC](https://community.fibery.io/t/regex-to-verify-a-field-entry/2105 "2025-11-19T22:45:48Z")

</div>

Hi there. Is there any way to verify a field entry? I would like to apply a regex to different fields (email, URL, phone number…) to validate it has the correct structure. Thanks

---

## [Show related field name](https://community.fibery.io/t/show-related-field-name/9828)

<div class="topic-metadata">

**Author:** [@jurgenappelo](https://community.fibery.io/u/jurgenappelo)\
**Replies:** 1\
**Last updated:** [October 28, 2025, 10:14pm UTC](https://community.fibery.io/t/show-related-field-name/9828 "2025-10-28T22:14:00Z")

</div>

One thing I miss is the names of related fields in the Fields overview. When I make more than one link to the same related entity, it is impossible to see which relation is mapped onto which field in the related table. S…

---

## [Fields: One-click convert single select to multi select and vice-versa](https://community.fibery.io/t/fields-one-click-convert-single-select-to-multi-select-and-vice-versa/9897)

<div class="topic-metadata">

**Author:** [@AdVhPkgKad](https://community.fibery.io/u/AdVhPkgKad)\
**Replies:** 0\
**Last updated:** [October 28, 2025, 2:51am UTC](https://community.fibery.io/t/fields-one-click-convert-single-select-to-multi-select-and-vice-versa/9897 "2025-10-28T02:51:11Z")

</div>

If a multi-select field has been set up, allow an automatic conversion to single select, and the other way. Where data would be lost, prevent users from changing the field type without first validating the existing data…

---

## [New field type: Code](https://community.fibery.io/t/new-field-type-code/8757)

<div class="topic-metadata">

**Author:** [@Yuri\_BC](https://community.fibery.io/u/Yuri_BC)\
**Replies:** 5\
**Last updated:** [October 26, 2025, 12:53pm UTC](https://community.fibery.io/t/new-field-type-code/8757 "2025-10-26T12:53:21Z")

</div>

I like to suggest the creation of a new field of type ‘Code’ Reason: Using a rich text document field always requires to include manually (or automatic) insertion of a code block (backticks) to store code. This is over…

---

## [On delete setting/strong relations for relation settings](https://community.fibery.io/t/on-delete-setting-strong-relations-for-relation-settings/8532)

<div class="topic-metadata">

**Author:** [@RonMakesSystems](https://community.fibery.io/u/RonMakesSystems)\
**Replies:** 5\
**Last updated:** [September 5, 2025, 9:11am UTC](https://community.fibery.io/t/on-delete-setting-strong-relations-for-relation-settings/8532 "2025-09-05T09:11:22Z")

</div>

Ability to set behaviour of what happens to related entities when sourse is deleted. Either: Prevent deletion (current default behaviour for when the related entity is related with required field) Cascade deletion (ca…

---

## [Voting in rows / Thumbs Up for entry](https://community.fibery.io/t/voting-in-rows-thumbs-up-for-entry/5114)

<div class="topic-metadata">

**Author:** [@Lukas\_Hroch](https://community.fibery.io/u/Lukas_Hroch)\
**Replies:** 17\
**Last updated:** [July 25, 2025, 11:00am UTC](https://community.fibery.io/t/voting-in-rows-thumbs-up-for-entry/5114 "2025-07-25T11:00:02Z")

</div>

In Coda.io, we have used column „Thumbs Up“ for woting about features. I would like to have this feature in Fibery too. Maybe there is workaround how to achieve one member can vote one times for one entry :slight\_smile: …

---

## [Set required field by formula / automation](https://community.fibery.io/t/set-required-field-by-formula-automation/8664)

<div class="topic-metadata">

**Author:** [@RonMakesSystems](https://community.fibery.io/u/RonMakesSystems)\
**Replies:** 0\
**Last updated:** [April 25, 2025, 8:33pm UTC](https://community.fibery.io/t/set-required-field-by-formula-automation/8664 "2025-04-25T20:33:53Z")

</div>

I have a situation where I want to set the field of the “Stage” by automation. Where it takes the first stage from the selected pipeline. Hence, it should not be set on creation, the automation sets it. But after this, i…

---

## [Getting all field values for an entity](https://community.fibery.io/t/getting-all-field-values-for-an-entity/2801)

<div class="topic-metadata">

**Author:** [@Chr1sG](https://community.fibery.io/u/Chr1sG)\
**Replies:** 3\
**Last updated:** [January 31, 2025, 6:02pm UTC](https://community.fibery.io/t/getting-all-field-values-for-an-entity/2801 "2025-01-31T18:02:34Z")

</div>

Here’s a little scripting snippet for how to retrieve all the information about an entity, without knowing or hard-coding the space name, database name or field names: const fibery = context.getService('fibery'); // get…

---

## [\[APPROVED\] Relationships filter](https://community.fibery.io/t/approved-relationships-filter/1364)

<div class="topic-metadata">

**Author:** [@Travis](https://community.fibery.io/u/Travis)\
**Replies:** 17\
**Last updated:** [January 17, 2024, 9:22pm UTC](https://community.fibery.io/t/approved-relationships-filter/1364 "2024-01-17T21:22:32Z")

</div>

It would be great to be able to create a Relation column that only shows a filtered subset of the relevant Type. So for example, a relation column that only shows Tasks that are already marked “done,” or Expenses that a…

---

## [Customize Fields via Rules](https://community.fibery.io/t/customize-fields-via-rules/1523)

<div class="topic-metadata">

**Author:** [@Matt\_Blais](https://community.fibery.io/u/Matt_Blais)\
**Replies:** 15\
**Last updated:** [September 22, 2023, 6:10am UTC](https://community.fibery.io/t/customize-fields-via-rules/1523 "2023-09-22T06:10:45Z")

</div>

I’d love the ability to customize the UI appearance of an entity’s fields – and most importantly, to be able to make some fields “read only”. A “read only” single-select field would be very useful to define an entity as…

[Next page](https://community.fibery.io/tag/flexible-domain/3.md?match_all_tags=true&page=1&tags%5B%5D=flexible-domain)
