Unable to create List Drop Down or Radio allowed values based field in Schemas

I have…

I’m submitting a…

  • [ ] Regression (a behavior that stopped working in a new release)
  • [x] Bug report
  • [ ] Performance issue
  • [ ] Documentation issue or request

Current behavior

Unable to create List Drop Down or Radio allowed values based field in Schemas

Old Bug: [SOLVED] String Input Dropdown Editor AllowedValues Error

Getting this error for creating List Allowed values

Expected behavior

Should be able to create list values

Minimal reproduction of the problem

  1. Self hosting on K8s using version: (7.0.2.0)

Environment

App Name:

  • [ ] Self hosted with docker
  • [ ] Self hosted with IIS
  • [x] Self hosted with other version
  • [ ] Cloud version

Version: [7.0.2]

Browser:

  • [ x] Chrome (desktop)
  • [ ] Chrome (Android)
  • [ ] Chrome (iOS)
  • [ ] Firefox
  • [ ] Safari (desktop)
  • [ ] Safari (iOS)
  • [ ] IE
  • [ ] Edge

Others:

I am pretty sure that this is an old bug that has been fixed already

@Sebastian I pasted the link also above which I found from the support forum around the old bug which you have fixed. But it seems to be back again.

Old Bug: [SOLVED] String Input Dropdown Editor AllowedValues Error

But I am still getting the error in self hosted (on K8s) using version: (7.0.2.0).

Is there a temporary hack like editing the JSON to allow for those values. I will make that change to atleast do a workaround on this one

I just tested it with Cloud Squidex it works fine there.

But it is a problem on self hosted (7.0.2.0). in K8s

As a work around I have looked up the JSON and attempting to use the below

{
            "name": "list1",
            "properties": {
                "isRequired": false,
                "isRequiredOnPublish": false,
                "isHalfWidth": false,
                "fieldType": "String",
                "createEnum": false,
                "editor": "Dropdown",
                "inlineEditable": false,
                "isEmbeddable": false,
                "isUnique": false,
                "allowedValues": [
                    "A",
                    "B",
                    "C"
                ],
                "contentType": "Unspecified"
            },
            "isLocked": false,
            "isHidden": false,
            "isDisabled": false,
            "partitioning": "invariant"
        }

@Sebastian so I temporarily managed to do a workaround this fix via the JSON schema configuration solving the issue for myself on selfhosted one. But USING THE UI to configure it is still an issue

Yes, 7.0.2.0 is not the newest version