Skip to content

Adding more than one uniqueness rule to a table sometimes allows you to save an invalid form #4800

Description

@emenslin

Describe the bug
Not sure entirely what is happening but it seems like when you create at least 2 uniqueness rules on one table it sometimes does not respect the uniqueness rules and the saveblocker gets ignored

To Reproduce
Steps to reproduce the behavior:

  1. Go to schema config-> any table (e.g. address)-> uniqueness rules
  2. Make sure there is at least 2 different uniqueness rules on the table
  3. Save
  4. Go to the data entry for that table
  5. Invalidate both fields
  6. Change one so it is valid (while the other should still be invalid)
  7. See you can save anyway

Expected behavior
You should not be able to save an invalid uniqueness rule.

Screenshots

6zItfELs66.mp4

Crash Report
Specify 7 Crash Report - 2024-04-16T20_54_06.887Z.txt

Please, also fill out the following information manually:

  • OS: Windows 11
  • Browser: Chrome
  • Specify 7 Version: edge
  • Database Name: lsumzmammals9823
  • Collection name: mammals
  • User Name: Spadmin

Metadata

Metadata

Assignees

Labels

1 - BugIncorrect behavior of the product2 - Schema ConfigIssues that are related to the Schema Config tool

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions