Key/Value Field: Key validation does not refresh after deleting conflicting key/value pair

[nicobytes]

Problem Statement

When adding a duplicate key to the key/value form, the form correctly shows a validation error (“This key already exists”). However, if the original conflicting entry is deleted, the validation state is not refreshed, and the error remains on the input, even though the key is no longer duplicated.

Steps to Reproduce

1. Add a new key/value pair with key: key3 and any value.
2. Attempt to add another entry with the same key: key3. The error message This key already exists appears correctly.
3. Delete the original key3 entry from the list.
4. Observe that the error message remains on the key input and it cannot be submitted again, even though the conflict has been resolved.

Acceptance Criteria

• When a key/value pair is deleted, any inputs currently showing a duplicate key error due to that key must revalidate.
• If the key is no longer present in the central list, the error should be removed and the input should be considered valid.
• The validation state must stay in sync with the actual list of key/value pairs managed centrally.

dotCMS Version

latest

Proposed Objective

Code Maintenance

Proposed Priority

Priority 4 - Trivial

External Links... Slack Conversations, Support Tickets, Figma Designs, etc.

No response

Assumptions & Initiation Needs

No response

Quality Assurance Notes & Workarounds

No response

Sub-Tasks & Estimates

No response