[Unique Field] : Validating Content Type with two Unique Fields is not being handled

[jcastro-dotcms]

Parent Issue

• Duplicate IDs in a Content Type Despite Unique Field Constraint #29459

Problem Statement

Content Types can have more than one Unique Field in their definition. When you have a Contentlet with different unique values, and create another Contentlet that uses one of the value from the other Contentlet, a raw SQL error ie being displayed to the user.

Steps to Reproduce

• In your docker-sompose.yml file, enable the feature flag:

DOT_FEATURE_FLAG_DB_UNIQUE_FIELD_VALIDATION: true

• Start dotCMS with the Full Starter.
• Create a Content Type with two unique Text fields:
  • Title
  • Number
• Create a Contentlet with the following data:
  • Title = 111
  • Number = 222
• Now, try to create another Contentlet with the following data:
  • Title = 111
  • Number = 555
• The following error shows up in the UI:

Acceptance Criteria

dotCMS must be able to validate as many Unique Fields as available.

dotCMS Version

Latest main.

Proposed Objective

Core Features

Proposed Priority

Priority 2 - Important

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

[github-actions]

PRs:

• Issue 30894 validating content type with two unique fields is not being handled #31108

[jcastro-dotcms]

INTERNAL QA: PASSED ✅

• Docker image: trunk_249c34d

When checking the uniqueness of fields flagged as unique, we're now returning an error as soon as the first unique field is duplicated. This makes the error easier to report and handle. Additionally, we're no longer getting the SQL stack trace in the error message in the UI.

[jcastro-dotcms]

This code fix was tested in the Authoring server, and it worked as expected.