# Cannot create field (in workflow)

**URL:** <https://community.fibery.io/t/cannot-create-field-in-workflow/4160>\
**Category:** Bugs & Issues\
**Created:** [March 21, 2023, 10:57am UTC](https://community.fibery.io/t/cannot-create-field-in-workflow/4160 "2023-03-21T10:57:34Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![Michel\_Daviot](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/michel_daviot/32/6094_2.png) [@Michel\_Daviot](https://community.fibery.io/u/Michel_Daviot)\
**Post date:** [March 21, 2023, 10:57am UTC](https://community.fibery.io/t/cannot-create-field-in-workflow/4160/1 "2023-03-21T10:57:34Z")

</div>

Hi,

I was trying to create a new field in the entity used for a workflow state. The field is single select.

I’ve got this error message:

```auto
Cannot create Simplifié field
Invalid schema: Invalid database names: workflow/Simplifié_workflow/state_Produit/Solution_acl, workflow/Simplifié_workflow/state_Produit/Solution. Cause: Invalid database names: workflow/Simplifié_workflow/state_Produit/Solution_acl, workflow/Simplifié_workflow/state_Produit/Solution.

```

 ![image](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/9/9dbea2d7284bd5d37f4eaa6b2f5ece7c123f9ab8.png)

My Use Case : I have a long development workflow (Kanban like) with about 12 steps. I wanted to display a simplified state in the board I show to internal customers.

---

<div class="post-metadata">

**Author:** ![Michel\_Daviot](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/michel_daviot/32/6094_2.png) [@Michel\_Daviot](https://community.fibery.io/u/Michel_Daviot)\
**Post date:** [March 21, 2023, 10:59am UTC](https://community.fibery.io/t/cannot-create-field-in-workflow/4160/2 "2023-03-21T10:59:28Z")

</div>

in case this helps :

```auto

[
    {
        "success": false,
        "result": {
            "name": "entity.error/schema-invalid",
            "message": "Invalid schema: Invalid database names: workflow/Simplifié_workflow/state_Produit/Solution_acl, workflow/Simplifié_workflow/state_Produit/Solution.\nCause: Invalid database names: workflow/Simplifié_workflow/state_Produit/Solution_acl, workflow/Simplifié_workflow/state_Produit/Solution.",
            "data": {
                "top": {
                    "error/name": "entity.error/schema-invalid"
                },
                "cause": {
                    "error/name": "entity.error/schema-type-name-invalid",
                    "types": [
                        "workflow/Simplifié_workflow/state_Produit/Solution_acl",
                        "workflow/Simplifié_workflow/state_Produit/Solution"
                    ]
                }
            },
            "via": [
                {
                    "type": "clojure.lang.ExceptionInfo",
                    "message": "Invalid schema: Invalid database names: workflow/Simplifié_workflow/state_Produit/Solution_acl, workflow/Simplifié_workflow/state_Produit/Solution.",
                    "data": {
                        "error/name": "entity.error/schema-invalid"
                    },
                    "at": [
                        "core.ex$ex_info",
                        "invokeStatic",
                        "ex.clj",
                        89
                    ]
                },
                {
                    "type": "clojure.lang.ExceptionInfo",
                    "message": "Invalid database names: workflow/Simplifié_workflow/state_Produit/Solution_acl, workflow/Simplifié_workflow/state_Produit/Solution.",
                    "data": {
                        "error/name": "entity.error/schema-type-name-invalid",
                        "types": [
                            "workflow/Simplifié_workflow/state_Produit/Solution_acl",
                            "workflow/Simplifié_workflow/state_Produit/Solution"
                        ]
                    },
                    "at": [
                        "core.ex$ex_info",
                        "invokeStatic",
                        "ex.clj",
                        89
                    ]
                }
            ]
        }
    }
]

```

---

<div class="post-metadata">

**Author:** ![Michel\_Daviot](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/michel_daviot/32/6094_2.png) [@Michel\_Daviot](https://community.fibery.io/u/Michel_Daviot)\
**Post date:** [March 21, 2023, 11:01am UTC](https://community.fibery.io/t/cannot-create-field-in-workflow/4160/3 "2023-03-21T11:01:36Z")

</div>

Similar issue when I try to create a relation to another database here

```auto
Invalid schema: Unexpected field names: {"field":"user/state_Produit/Solution","holder-type":"Colisweb/Projet"}. Cause: Unexpected field names: {"field":"user/state_Produit/Solution","holder-type":"Colisweb/Projet"}.

```

---

<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:** [March 21, 2023, 3:18pm UTC](https://community.fibery.io/t/cannot-create-field-in-workflow/4160/4 "2023-03-21T15:18:33Z")

</div>

This is not supported, it is not possible to create a single-select inside a single-select. Why not add a Text field and put some value in it?

---

<div class="post-metadata">

**Author:** ![Michel\_Daviot](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/michel_daviot/32/6094_2.png) [@Michel\_Daviot](https://community.fibery.io/u/Michel_Daviot)\
**Post date:** [March 21, 2023, 4:20pm UTC](https://community.fibery.io/t/cannot-create-field-in-workflow/4160/5 "2023-03-21T16:20:55Z")

</div>

The workaround I tried : using a text field in the state entity  
It does not work because I cannot use a text field as a board column

![image](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/f/fb37bcc41fe32130a6535e8de8fba39aa6322e09.png)

(I forgot to post this a few hours ago)

---

<div class="post-metadata">

**Author:** ![Michel\_Daviot](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/michel_daviot/32/6094_2.png) [@Michel\_Daviot](https://community.fibery.io/u/Michel_Daviot)\
**Post date:** [March 21, 2023, 4:21pm UTC](https://community.fibery.io/t/cannot-create-field-in-workflow/4160/6 "2023-03-21T16:21:52Z")

</div>

Even if this is not supported, I suggest to remove the option from the list of new fields, or at least to have a more user-friendly error message.

---

<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:** [March 21, 2023, 4:38pm UTC](https://community.fibery.io/t/cannot-create-field-in-workflow/4160/7 "2023-03-21T16:38:42Z")

</div>

Agreed about the possible ux improvements.  
But what are you trying to ultimately achieve?

---

<div class="post-metadata">

**Author:** ![Michel\_Daviot](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/michel_daviot/32/6094_2.png) [@Michel\_Daviot](https://community.fibery.io/u/Michel_Daviot)\
**Post date:** [March 21, 2023, 5:05pm UTC](https://community.fibery.io/t/cannot-create-field-in-workflow/4160/8 "2023-03-21T17:05:48Z")

</div>

> [@Michel\_Daviot](#):
>
> My Use Case : I have a long development workflow (Kanban like) with about 12 steps. I wanted to display a simplified state in the board I show to internal customers.

Basically I want to regroup 12 statuses in 4 for a different group of users