Single select dropdown option labels not visible in app

English Forum Issue Report
1

* Describe the bug

I have configured a single select ‘status’ field in a collection and configured the options. In the configuration field everything looks good, but in the frontend the option label text is not visible.

* Environment

  • NocoBase version:
    1.7.15
  • Database type and version:
    Postgres
  • OS:
    Ubuntu
  • Deployment Methods:
    Docker
    nocobase/nocobase:latest

* How To Reproduce

4fa84d15e5284adbf22f1e938208c41cdb3f49a09707b6646df2e82f8e394c15
4fa84d15e5284adbf22f1e938208c41cdb3f49a09707b6646df2e82f8e394c151452×568 12.2 KB

3f03e3f0e4aab34a4afbfeb9ab489c9b53ec5589166d35142593941d9d429ad4
3f03e3f0e4aab34a4afbfeb9ab489c9b53ec5589166d35142593941d9d429ad41470×1706 175 KB

Additional info

On mobile view the select option is visible, but another error screen shows up.

878600f0d44ffac72908083e9d27aa04dc87bf3c0019e8026676763c3371cfdc
878600f0d44ffac72908083e9d27aa04dc87bf3c0019e8026676763c3371cfdc1452×568 50.3 KB

I had the status field set up as an association field before, linked to a wo_status collection. I deleted that and created a single select status field so it could be used in a kanban block.

2

Have you created a association field called “status” before?

Will deleting and re-adding this “status” field in the form solve the problem?

3

I tried deleting and re-adding but I get the same error. I then added it with a different field name and it works fine. There seems to be some kind of bug where after deleting an relation field with a specific name, adding a new field with the same field name creates an issue.

4

I just found the source of the issue: there was a workflow still avtive that relied on the field that was deleted. Apologies for the confusion. Perhaps it would be an idea to have a warning when a user tries to delete a field that is part of a workflow?