Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Not null constraint not met when multiple values selected in drop down selector widget #3418

Closed
raherin opened this issue May 10, 2024 · 1 comment · Fixed by #3446
Closed
Assignees
Milestone

Comments

@raherin
Copy link

raherin commented May 10, 2024

When using the 'Value relation' widget and the 'Allow multiple selections' option is selected and the 'Not null' constraint is used, the app will fail to record the values selected if multiple values are chosen. The "Field should not be empty" error will show if the user selects multiple values in the drop-down menu. In order to remove the error message, the user must open the menu again and deselect one of the options and then select it again:

Screen_Recording_20240510_182332.mp4

I have created a project to demonstrate the error: support/drop-menu-test

To reproduce the problem:

  1. download the project on the mobile app
  2. open the project
  3. press the 'Add' button to record a new feature
  4. press 'Record' to create the feature
  5. click on the drop-down menu on the 'path' field
  6. select multiple options and press 'Confirm selection'
  7. the 'Field should not be empty' error will show
  8. reopen the drop-down menu
  9. deselect one of the options and then select it again
  10. press 'Confirm selection'
@jozef-budac
Copy link

I was not able to simulate the problem on the current 2024.2.0 RC. @raherin , can you also verify, that it is fixed?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants