You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Please confirm if bug report does NOT exists already ?
I confirm there is no existing issue for this
Steps to reproduce ?
I don't know that you can reproduce this, it's only happening with my existing tables and if I try with a new field, it's fine. It may be related to an update with existing data.
In my base, I have several tables with single select fields. These have options like "Morning" and "Night" as the only options. I don't often insert manually into these tables but since I'm also having API issues, I have to manually insert and I'm seeing this behavior when I try to select from a drop down.
Nothing has changed in these tables for over a year, the only thing that has changed is updates to the container and unfortunately I can't be sure when it started happening.
For instance, in the above example, I click the field, it drops down and shows Morning or Night, but when I pick one, it throws this error:
The logs show this :
nocodb | BadRequest [Error]: Invalid option "Morning" provided for column "starting_dose". Valid options are "'Morning', 'Night'"
nocodb | at NcError.badRequest (/usr/src/app/docker/main.js:2:989112)
nocodb | at BaseModelSqlv2.validateOptions (/usr/src/app/docker/main.js:2:533048)
nocodb | at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
nocodb | at async BaseModelSqlv2.validate (/usr/src/app/docker/main.js:2:532039)
nocodb | at async BaseModelSqlv2.updateByPk (/usr/src/app/docker/main.js:2:515144)
nocodb | at async DatasService.dataUpdate (/usr/src/app/docker/main.js:2:1628472)
nocodb | at async DataAliasController.dataUpdate (/usr/src/app/docker/main.js:2:366773)
This will of course not save the field when this happens.
If I edit the field and add an optoins, save, then delete the new option, the problem goes away so there's a workaround at least.
Please confirm if bug report does NOT exists already ?
Steps to reproduce ?
I don't know that you can reproduce this, it's only happening with my existing tables and if I try with a new field, it's fine. It may be related to an update with existing data.
In my base, I have several tables with single select fields. These have options like "Morning" and "Night" as the only options. I don't often insert manually into these tables but since I'm also having API issues, I have to manually insert and I'm seeing this behavior when I try to select from a drop down.
Nothing has changed in these tables for over a year, the only thing that has changed is updates to the container and unfortunately I can't be sure when it started happening.
For instance, in the above example, I click the field, it drops down and shows Morning or Night, but when I pick one, it throws this error:
The logs show this :
This will of course not save the field when this happens.
If I edit the field and add an optoins, save, then delete the new option, the problem goes away so there's a workaround at least.
Desired Behavior
The drop down select inserts the field I chose.
Project Details
Node: v18.17.1
Arch: x64
Platform: linux
Docker: true
RootDB: pg
PackageVersion: 0.202.9
Attachments
No response
The text was updated successfully, but these errors were encountered: